GKE golden path: production-ready cluster defaults and readiness checklists
@google's opinionated GKE Autopilot configuration β production defaults, Day-0 vs Day-1 decisions, guardrails and readiness checklists
- What
- @google's opinionated GKE Autopilot configuration β production defaults, Day-0 vs Day-1 decisions, guardrails and readiness checklists
- Cost
- Free
- Needs
- a billed Google Cloud project with GKE access (clusters incur management fees and workload costs β no usable free tier); MCP tools or gcloud/kubectl configured; the skill itself is guidance only, it does not provision resources
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
Curated by Skill Harbor β π³ **Paid API required / API payante requise** β GKE clusters run on a billed Google Cloud project (cluster management fees and workload resources are billed); the skill itself is guidance. @google's official golden-path configuration for production GKE clusters: an always-applied defaults table (Autopilot enabled, private nodes, private-endpoint enforcement, Secret Manager rotation, insecure RBAC bindings off, workload identity, ADVANCED_DATAPATH, Cloud DNS, Pod Security Standards `restricted` on production namespaces, shielded instances, stateful HA), a customer-configurable-settings table with deviation guidance (max pods per node, boot disk type, machine type, maintenance exclusions), production-readiness checklists, a Day-0 vs Day-1 framing that flags hard-to-change decisions (networking, private nodes, IP allocation), and guardrails β never request or output secrets, tool preference MCP > gcloud > kubectl, document every Day-0 choice and golden-path deviation. By @google, listed here with credit to its creator. Honest caveats: guidance and defaults only β it does not provision or change cloud resources itself; product defaults may drift from Google Cloud docs; requires GCP access for anything real. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a billed Google Cloud project with GKE access (clusters incur management fees and workload costs β no usable free tier); MCP tools or gcloud/kubectl configured; the skill itself is guidance only, it does not provision resources Install "GKE golden path: production-ready cluster defaults and readiness checklists" for me. It gives the agent @google's official GKE golden-path configuration: the always-applied production defaults table, the customer-configurable-settings table with deviation guidance, production-readiness checklists, the Day-0 vs Day-1 framing for hard-to-change decisions, and the guardrails (no secrets handling, MCP > gcloud > kubectl tool preference, documented decisions). Apache-2.0 licensed. Repository: https://github.com/google/skills/blob/main/skills/cloud/gke-golden-path/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "gke-golden-path". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. gather the required inputs β project ID, region, cluster name, environment type β and confirm the Day-0 decisions before any real provisioning). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.