Skip to content

Document GKE cluster name restrictions#249

Open
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/gke-cluster-name-restrictions-1778680614
Open

Document GKE cluster name restrictions#249
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/gke-cluster-name-restrictions-1778680614

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented May 13, 2026

Summary

Documents new validation rules for GKE cluster names that reject reserved Google Cloud Storage substrings (google, g00gle, goog, g00g) at cluster creation time.

Why

A recent platform change adds up-front validation for GKE cluster names. Because Porter derives GCS bucket names (for example, for Loki object storage) from the cluster name, and GCS hard-rejects bucket names containing these substrings, a cluster using a name like rajeev-google would silently fail to fully provision and the only recovery path was recreating the cluster. The platform now rejects these names at contract validation time so users fail fast on cluster create.

Changes

  • Adds a warning to the "Configure your cluster" step in the GCP tab of the cluster creation guide explaining the naming rules and the reserved substrings.
  • Adds a troubleshooting accordion for "Cluster name validation failed" with the full rule list and example valid/invalid names.

Triggering PR

porter-dev/code#5432 — adds GKEValues.Validate rejection for cluster names containing google, g00gle, goog, or g00g.

@mintlify
Copy link
Copy Markdown
Contributor Author

mintlify Bot commented May 13, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
porter 🟢 Ready View Preview May 13, 2026, 2:51 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants