Discussion: Clusters naming convention
As we are moving towards disposable infrastructure and multi-cluster/multi-region setup, it's necessary to come up with reasonable naming convention for clusters
Suggested endpoint naming convention:
- Name should clearly represent the cluster purpose and position of the cluster in the entire infrastructure.
- Example:
gke-pre-us-central1-a-gitlab-1
where:- gke - for gke cloud, aws - for aws
- pre - environment
- us-central1 - region
- a - availability zone (optional)
- gitlab - cluster type,
gitlab
for gitlab instance,ops
for ops cluster for example - 1 - cluster id, as we can have more than one gitlab clusters in one single zone/region
Please provide your feedback of what would be the most ideal naming convention.
Edited by Vladimir Glafirov