skills.rest
wangx7
wangx7COMMUNITY
Explore all skills by this author →
GitHub

gke-upgrades

Generate GKE upgrade plans and runbooks with gcloud commands.

Updated Jun 26, 2026
Search Tags:#kubernetes#gcloud#gpu workloads#gke#maintenance windows#cluster upgrades#rollout sequencing
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill gke-upgrades
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gke-upgrades
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/cloud/gke-upgrades
Command: npx skills add https://github.com/wangx7/skills-collection --skill gke-upgrades

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GKE cluster upgrades involve complex coordination of version compatibility, workload safety, maintenance windows, and rollback procedures, with high risk of service disruption if mishandled. This Skill eliminates manual overhead and guesswork by providing structured, environment-specific guidance for all GKE lifecycle management tasks.

Core Features & Use Cases

  • Upgrade Planning & Execution: Generates tailored upgrade plans, step-by-step runbooks with valid gcloud commands, and node pool upgrade strategies (surge, blue-green) for both Standard and Autopilot clusters.
  • Maintenance Management: Provides guidance for release channel selection, maintenance window configuration, exclusion rules, and Rollout Sequencing to automate safe, scheduled upgrades across dev/staging/prod environments.
  • Troubleshooting & Validation: Includes systematic checks for stuck upgrades, GPU/TPU workload compatibility, and pre/post-upgrade checklists to minimize downtime and ensure workload readiness. Use Case: If you need to upgrade a production GKE cluster running stateful databases and GPU workloads, this Skill creates a customized runbook with surge settings, PDB validation, and rollback procedures to avoid service disruption.

Quick Start

Use the gke-upgrades skill to create a complete upgrade plan and runbook for my production GKE Standard cluster running version 1.29, targeting version 1.30, with stateful PostgreSQL workloads and GPU node pools.

Frequently Asked Questions about gke-upgrades

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a GKE cluster upgrade without causing downtime for stateful workloads?▼

Planning a GKE cluster upgrade for stateful workloads requires tailored runbooks with surge settings, PodDisruptionBudget validation, and rollback procedures to ensure workload safety. This structured approach minimizes service disruption risks during node pool upgrades.

What's the best way to configure GKE maintenance windows and release channels across environments?▼

The best way to configure GKE maintenance windows is by selecting release channels, setting maintenance exclusions, and applying Rollout Sequencing to automate safe scheduled upgrades across dev, staging, and production environments for both Standard and Autopilot clusters.

Does this GKE upgrade guidance support GPU and TPU node pools?▼

Yes, GKE upgrade guidance supports GPU and TPU node pools by providing systematic compatibility checks and workload-specific troubleshooting. It ensures specialized hardware workloads maintain readiness and compliance with GKE best practices throughout the upgrade lifecycle.

How do I troubleshoot a stuck GKE cluster upgrade?▼

To troubleshoot a stuck GKE cluster upgrade, run systematic checks for node pool surge limits, PDB conflicts, and workload compatibility issues. Using pre and post-upgrade checklists helps identify blocking factors and validate workload readiness to safely resume the upgrade.

Can I use blue-green upgrades for GKE Autopilot clusters?▼

Yes, blue-green upgrade strategies are supported for GKE Autopilot clusters alongside surge configurations. The guidance covers node pool strategy selection for both Standard and Autopilot clusters to ensure safe, environment-specific workload transitions during maintenance operations.

Why are my GKE node pool upgrades failing during maintenance windows?▼

GKE node pool upgrades fail during maintenance windows due to insufficient surge upgrade settings, PodDisruptionBudget conflicts, or workload incompatibility. Validating pre-upgrade checklists and adjusting maintenance exclusion rules ensures workload safety and resolves blocking upgrade conditions.

Related Skills

Explore More Software Engineering Skills→
ssmleossmleo

gke-upgrades

Automate GKE cluster upgrade planning and execution with gcloud and kubectl.

Community
Advanced
googlegoogle
17.1k

gke-upgrades

Generate GKE cluster upgrade plans, runbooks, and checklists.

Official
Advanced
wangx7wangx7

gke-reliability

Configure GKE Pod Disruption Budgets, health probes, and topology spread constraints.

Community
Intermediate
gke-labsgke-labs
42

gke-cluster-lifecycle

Manage Google Kubernetes Engine cluster lifecycle, upgrades, and decommissioning.

Official
Advanced