gke-reliability

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

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill gke-reliability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-reliability
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/cloud/gke-reliability
Command: npx skills add https://github.com/wangx7/skills-collection --skill gke-reliability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GKE workloads frequently experience avoidable downtime from unplanned voluntary disruptions, missing health checks, and poor failure domain distribution, leading to service outages and degraded user experience for production applications.

Core Features & Use Cases

  • Pod Disruption Budgets (PDBs): Configure minimum availability guarantees for workloads during voluntary disruptions like node upgrades and autoscaler scale-down events.
  • Health Probe Setup: Implement liveness, readiness, and startup probes to validate container health, manage traffic routing, and prevent premature restarts for slow-starting applications.
  • Failure Domain Resilience: Use topology spread constraints and replica best practices to distribute workloads across zones and nodes, surviving zone and node failures.
  • Use Case: A team running production stateless APIs on GKE can use this skill to implement all required reliability configurations to maintain 99.9% uptime during cluster maintenance and zone outages.

Quick Start

Use the gke-reliability skill to configure production-grade reliability settings for your GKE deployment, including PDBs, health probes, and zone spread constraints to eliminate avoidable downtime.

Frequently Asked Questions about gke-reliability

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

FAQPage Schema
How do I prevent GKE workload downtime during node upgrades and zone outages?

To prevent GKE downtime during disruptions, configure Pod Disruption Budgets and topology spread constraints to guarantee minimum availability and distribute pods across failure domains.

What's the best way to configure health probes for slow-starting applications in GKE?

Configuring GKE health probes requires setting up startup probes to prevent premature restarts, alongside liveness and readiness probes to validate container health and manage traffic routing effectively.

How do topology spread constraints improve high availability in Google Kubernetes Engine?

Topology spread constraints improve Google Kubernetes Engine high availability by distributing pod replicas across nodes and zones, ensuring workloads survive localized node failures and zone outages.

When do I need a Pod Disruption Budget for my GKE production workloads?

You need a Pod Disruption Budget for GKE production workloads to maintain minimum service availability during voluntary disruptions like node upgrades and autoscaler scale-down events.

Can I use this approach to achieve 99.9% uptime for stateless APIs on GKE?

Yes, implementing production-grade reliability settings like PDBs, health probes, and zone spread constraints enables stateless APIs on GKE to maintain 99.9% uptime during cluster maintenance.