Cluster Naming Convention

Cluster names should be predictable.

Why naming matters

At ten clusters, naming feels like a non-issue. At fifty, ad-hoc names like cluster-prod-2 and main-east become a productivity tax. Engineers grep, lookup, and second-guess constantly.

Naming encodes context. A good name tells you environment, region, purpose, and ownership at a glance. The on-call engineer triaging an incident reads the name and knows which dashboards to open.

Consistency aids automation. CI scripts that target prod-* match exactly the prod clusters. Without a naming convention, CI matches are fragile and dangerous.

The pattern

Format: {env}-{region}-{purpose}-{n}. Examples: prod-us-east-1-app-1, staging-eu-west-1-batch-1, dev-shared-1.

env is the environment: prod, staging, qa, dev. Region matches the cloud provider's region label exactly.

Purpose is one word: app, batch, ml, data. Stick to a small enumerated set. The number suffix allows for capacity expansion.

Beyond the name: tags

Tags carry the metadata the name cannot fit. team, owner, contact, cost-center, expiry. These are queryable in cloud APIs.

Naming convention plus tagging convention is the full story. The name is the primary key; tags are the metadata.

IaC enforces both. Terraform module rejects launches without proper name and required tags. CI fails the PR if missing.

Migration strategy

Existing clusters get renamed at next replacement. Forcing immediate renames disrupts; treat the convention as the standard for new clusters.

Document deviations explicitly. cluster-old-prod-2 is allowed to exist with a written exception; nobody is confused.

Quarterly drift report. Clusters that don't match the convention are flagged. Owners explain or rename.

Scaling considerations

Above 100 clusters, even good conventions hit limits. Add suffix for finer-grained purpose. prod-us-east-1-checkout-1 splits from prod-us-east-1-app-1.

Cluster discovery becomes its own service. Internal tool maps purposes to cluster names. Engineers query the tool, not the cluster list.

Federation considerations. Multi-cluster control planes (Karmada, Anthos) use cluster names as identifiers. Convention here is even more important.