gke-upgrades
Plans, executes, and validates Google Kubernetes Engine (GKE) cluster upgrades and maintenance operations for both Standard and Autopilot clusters. Produces upgrade plans, pre/post-upgrade checklists, maintenance runbooks with gcloud commands, release channel strategy, and troubleshooting guides. Handles node pool upgrade strategies (surge, blue-green), version compatibility, PDB management, and workload-specific concerns (stateful, GPU, operators). Use this skill whenever the user mentions GKE
Security Assessment
About gke-upgrades
GKE Upgrades & Maintenance is an operations runbook skill for planning, executing, and validating Google Kubernetes Engine cluster upgrades and maintenance across both Standard and Autopilot clusters. It solves the risk-heavy problem of Kubernetes version management: producing environment-specific upgrade plans, pre/post checklists, and maintenance runbooks with gcloud commands rather than generic advice.
The skill first gathers context (cluster mode, current/target versions and version skew, release channel, environment topology and rollout sequencing, and workload sensitivity), then applies core principles: sequential control-plane upgrades with skip-level node pools, control plane first, dev/staging before production, workload-aware strategy, release channels over deprecated static versioning, and canary ordering of node pools. It documents release-channel trade-offs (Rapid, Regular, Stable, Extended), node-pool strategies (surge and blue-green), PDB management, and rollback constraints. A troubleshooting reference walks stuck or failing upgrades in order, covering PDBs blocking drain, resource constraints, bare pods, admission webhooks, PVC attachment, long termination grace periods, GKE-level stalls, stockouts during time-critical upgrades (including credential rotation and DNS-endpoint enablement), and GPU driver regressions, each with diagnosis commands and fixes. A runbook template and checklists round out the deliverables.
It targets platform/SRE and DevOps engineers and cluster operators responsible for GKE lifecycle management. The commands it provides operate on the user's own clusters via gcloud and kubectl; some troubleshooting steps temporarily relax PDBs or remove admission webhooks during a maintenance window, which are standard, reversible operational remediations that the skill instructs to restore afterward.
FAQ
What deliverables does it produce?
Environment-specific upgrade plans, pre- and post-upgrade checklists, maintenance runbooks with gcloud commands, release-channel strategy, and troubleshooting guides, tailored to your cluster mode, channel, version, and workloads.
What context does it need first?
Cluster mode (Standard vs Autopilot), current and target versions and skew, release channel, environment topology and whether Rollout Sequencing is used, and workload sensitivity (StatefulSets, databases, GPU, batch).
What are the key upgrade ordering rules?
Control plane upgrades are sequential and must precede node pools; node pools support skip-level upgrades and can trail by up to two minor versions; upgrade dev/staging before production; and upgrade non-critical/stateless pools first as a canary.
How does it handle stuck upgrades?
The troubleshooting reference works through common causes in order (PDBs blocking drain, resource constraints, bare pods, admission webhooks, PVC issues, GKE-level stalls, stockouts, GPU driver regressions) with diagnosis commands and fixes, and instructs restoring temporarily changed resources afterward.
What is out of scope?
Cluster creation, application onboarding, general networking/routing setup, and security-policy configuration; the skill directs those to gke-basics or other GKE skills.
Install gke-upgrades
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
google/skills