View original page

GKE Capacity Triage

DevOps & Infrastructure

Triage a GKE workload stuck Pending because node provisioning fails with a Compute Engine capacity error (ZONE_RESOURCE_POOL_EXHAUSTED, "GCE out of resources", scale.up.error.out.of.resources) or a quota error (QUOTA_EXCEEDED). Separates resource unavailability from quota limits and configuration causes, explains why the ComputeClass fallback didn't help, and gives the documented ComputeClass, Pod-level, or cluster-level fix to apply. Use when a user pastes a scale-up failure alert or asks why Pods are stuck Pending, lack nodes, or hit a stockout. Don't use for Standard-cluster TPU slices whose specific reservation lacks consumable instances, such as one held by unhealthy node pools with auto-repair disabled (gke-ai-troubleshooting-tpu-reservation-stockout), autoscaler enablement, profiles, or scale-down (gke-cluster-autoscaler), ComputeClass authoring without an incident (gke-compute-classes), Pods already on a node (gke-workload-troubleshooting, gke-storage-troubleshooting), or non-GKE clusters.

Publisher / source

Google Skills (Verified)

Upstream record

google/skills

Version

Version 1

Published

2026-11-17

Publication review

Approved for publication

Content fingerprint

efa529611ddcbd27c7b41b7fbdb3cbc1aba8a79b0175402e9d342bdf738943e8

Review before you use it

Publication approval is a recorded review state, not a guarantee of safe execution. Check the upstream license, required tools and permissions, and test in your intended client.

Sign in to inspect the full instructions and download the SKILL.md file. This public page contains metadata only.

Open skill in your workspace


Source: https://prompeteer.ai/skills-hub/2de49c88-e54e-4034-b9bf-066eed0e427d