gke-reliability

Name: gke-reliability
Availability: InStock
Author: ssmleo

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

Updated Jul 4, 2026

Search Tags:#reliability #GKE #health probes #Pod Disruption Budgets #topology spread constraints

Ready to run

npx skills add https://github.com/ssmleo/govfolio --skill gke-reliability-ssmleo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gke-reliability
Source: https://github.com/ssmleo/govfolio/tree/main/.agents/skills/gke-reliability
Command: npx skills add https://github.com/ssmleo/govfolio --skill gke-reliability-ssmleo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring high availability and reliability for GKE workloads, helping to configure Pod Disruption Budgets (PDBs), health probes, and topology spread constraints.

Core Features & Use Cases

Pod Disruption Budgets (PDBs): Ensures minimum pod availability during disruptions.
Health Probes: Configures liveness, readiness, and startup probes for containers.
Topology Spread Constraints: Distributes pods across zones and nodes for resilience.
Use Case: For a GKE cluster, this Skill can be used to set up PDBs for a Deployment, configure health probes for a container, and apply topology spread constraints to ensure pod distribution across failure domains.

Quick Start

Use the gke-reliability skill to set up Pod Disruption Budgets for a Deployment named 'my-app'.

Frequently Asked Questions about gke-reliability

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

FAQPage Schema

How do I configure Pod Disruption Budgets for a GKE Deployment?▼

To configure Pod Disruption Budgets (PDBs) for a GKE Deployment, you set rules that ensure minimum pod availability during disruptions. This guarantees your application maintains a required number of healthy replicas during voluntary disruptions.

What is the best way to distribute GKE pods across zones and nodes?▼

The best way to distribute GKE pods across zones and nodes is by applying topology spread constraints. This mechanism schedules pods evenly across failure domains, enhancing cluster resilience against zone or node-level outages.

How do health probes improve GKE workload reliability?▼

Health probes improve GKE workload reliability by monitoring container states through liveness, readiness, and startup checks. They ensure traffic routes only to ready containers and restart unresponsive ones automatically.

Do I need Kubernetes API access to set up topology spread constraints?▼

Yes, you need Kubernetes API access to apply topology spread constraints. Configuring these constraints and pod disruption budgets requires direct interaction with the GKE cluster architecture.

When should I use Pod Disruption Budgets in Google Kubernetes Engine?▼

You should use Pod Disruption Budgets in Google Kubernetes Engine whenever your application requires high availability. PDBs prevent voluntary disruptions from taking down too many pods simultaneously, ensuring continuous service.

Can I set up liveness and readiness probes for containers hosted on GKE?▼

Yes, you can set up liveness, readiness, and startup probes for containers hosted on Google Kubernetes Engine. Configuring these health probes ensures your workload reliability by managing traffic routing and container restarts.