gke-ai-troubleshooting-tpu-reservation-stockout
Diagnose and resolve cluster-wide GKE TPU node pool creation or scale-up failures caused by Compute Engine reservation stockouts (GCE_STOCKOUT…
Skill by googleOfficial
Chalk Labs
Need help deploying gke-ai-troubleshooting-tpu-reservation-stockout?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/google-gke-ai-troubleshooting-tpu-reservation-stockout
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/gke-ai-troubleshooting-tpu-reservation-stockout
What's inside
- Skill name
gke-ai-troubleshooting-tpu-reservation-stockout- Description
- Diagnose and resolve cluster-wide GKE TPU node pool creation or scale-up failures caused by Compute Engine reservation stockouts (GCE_STOCKOUT, ZONE_RESOURCE_POOL_EXHAUSTED) when existing unhealthy or NotReady TPU node pools in the cluster have node auto-repair disabled and hold reserved TPU capacity. Use when TPU node pool creation or scale-up fails with GCE_STOCKOUT, ZONE_RESOURCE_POOL_EXHAUSTED, or ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS despite having a specific Compute Engine TPU reservation. Don't use for general pod scheduling without a TPU reservation or workload-level container crashes.
- License
- Apache-2.0
- Metadata
- version: 1.0.1 · category: Containers
- Instructions
- 275 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- attribution.md · references/
SKILL.md (first lines)
# Troubleshoot GKE TPU reservation stockouts caused by leaked node pool capacity
Use this skill to diagnose and resolve GKE TPU node pool creation or scale-up
failures that fail with `GCE_STOCKOUT`, `ZONE_RESOURCE_POOL_EXHAUSTED`, or
`ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS` (or queue due to lack of capacity)
even though they target a specific Compute Engine TPU reservation.
If node auto-repair is disabled on an existing TPU node pool, GKE doesn't repair
its nodes when they become `NotReady`. While their VMs are still running, they
keep consuming slots in the reservation (`inUseCount` is the number of running
instances that consume the reservation). Per
[Ensure reservation availability](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/tpus.md.txt),
the reservation must have sufficient available TPU chips at the time of node
pool creation, and per
[Multi-host TPU slice node pools](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/tpus.md.txt),
if GKE is unable to deploy one node in a slice, no nodes in the TPU slice node
pool are deployed. When the free slots in the reservation
(`specificReservation.count - specificReservation.inUseCount`; see
[Consumable instances in a reservation](https://docs.cloud.google.com/compute/docs/instances/reservations-view.md.txt))
are fewer than the number of nodes that the new TPU node pool needs, creation
fails with `GCE_STOCKOUT` or `ZONE_RESOURCE_POOL_EXHAUSTED` (or queues due to
lack of capacity).
## Attribution
**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you
MUST read [Usage Attribution](references/attribution.md). For commands executed
directly in the terminal (never in generated scripts, Terraform, or user code),
prefix `gcloud` with
`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gke-ai-troubleshooting-tpu-reservation-stockout)"`
and append `agent-skills/1.0 (skill:gke-ai-troubleshooting-tpu-reservation-stockout)` to `User-Agent` headers.
## Prerequisites
- **Required IAM Roles**:
- Logs Viewer (`roles/logging.viewer`): Query Cloud Audit Logs in Cloud
Logging.
- Monitoring Viewer (`roles/monitoring.viewer`): Query GKE node readiness
metrics in Cloud Monitoring.
- Kubernetes Engine Viewer (`roles/container.viewer`): Inspect GKE node pools
(`management.autoRepair`), cluster operations, and node conditions.
- Compute Viewer (`roles/compute.viewer`): Inspect Compute Engine reservation
utilization (`specificReservation.inUseCount` vs
`specificReservation.count`), consuming instances, and VM labels (including
in the reservation's owner project if using a shared reservation).
- For remediation (`[High Risk]` steps): Kubernetes Engine Cluster Admin
(`roles/container.clusterAdmin`)
- **API Enablement & Billing**:
- Ensure the target project has an active Google Cloud billing account
attached: `gcloud billing projects describe {project_id}`.
- Enable required APIs: `container.googleapis.com`, `compute.googleapis.com`,
`logging.googleapis.com`, and `monitoring.googleapis.com`.
- **CLI & Authentication Setup**:
- Install Google Cloud SDK (`gcloud`) and `kubectl`:
https://cloud.google.com/sdk/docs/install.
- **Cluster mode**: This skill applies to Standard clusters. Autopilot clusters
always auto-repair nodes, and you can't turn this off (see
[Settings for Autopilot and Standard](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair.md.txt)).
- **Reference Documentation**:
- [Auto-repair nodes](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair.md.txt)
(Sections: "Settings for Autopilot and Standard", "Repair criteria", "Node
repair process", "Verify node auto-repair is enabled for a Standard node
pool", "Node auto repair in TPU slice nodes", "Enable auto-repair for an
existing Standard node pool", "Get information about recent automated repair
events")
- [Troubleshoot GKE Standard node pools](https://docs.cloud.google.com/kubernetes-engine/docs/troubleshooting/node-pools.md.txt)
(Sections: "Issue: Node pool creation fails due to insufficient resources")
- [Troubleshoot TPUs in GKE](https://docs.cloud.google.com/kubernetes-engine/docs/troubleshooting/tpus.md.txt)
(Sections: "How GKE handles capacity issues", "Insufficient TPU resources to
satisfy the TPU request")
- [About TPUs in GKE](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/tpus.md.txt)
(Sections: "Multi-host TPU slice node pools")
- [Consuming reserved zonal resources](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/consuming-reservations.md.txt)
(Sections: "Consuming a specific shared reservation")
- [About reservations](https://docs.cloud.google.com/compute/docs/instances/reservations-overview.md.txt)
(Sections: "How reservations work")
- [View reservations or future reservation requests](https://docs.cloud.google.com/compute/docs/instances/reservations-view.md.txt)
(Sections: "Limitations", "View reservations", "Consumable instances in a
reservation", "View a list of instances that are consuming a reservation")
- [Organize resources using labels](https://docs.cloud.google.com/compute/docs/labeling-resources.md.txt)
(Sections: "View labels")
- [Create and manage cluster and node pool labels](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/creating-managing-labels.md.txt)
(Sections: "Automatically applied labels")
- [Deploy TPU workloads in GKE Standard](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/tpus.md.txt)
(Sections: "Ensure reservation availability", "Monitor health metrics for
TPU nodes and node pools", "Configure auto repair for TPU slice nodes")
- [Add and manage node pools](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-pools.md.txt)
(Sections: "Delete a node pool")
> **Read-only rule**: Run read-only diagnostic commands only. Never drain,
> delete, or re-create nodes, or run any other command that changes the cluster.
> Give the user any fix to apply themselves.
When you recommend a fix, link the doc section that describes it.
---
## Diagnostic workflow
### Step 0: Collect context and set the investigation window
Identify the following environment parameters from the user prompt or cluster
context:
- `{project_id}`, `{cluster_name}`, `{location}`, `{failing_nodepool_name}`,
`{reservation_name}`, `{reservation_project_id}` (the project that owns
`{reservation_name}`, which defaults to `{project_id}` for a single-project
reservation or is the owner project for a shared reservation; see
[Consuming a specific shared reservation](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/consuming-reservations.md.txt)),
`{zone}` (the zone of the reservation), and `{issue_time}`.
- **Time window**: By default, query a 60-minute window `[{issue_time} - 30m,
{issue_time} + 30m]` (`{start_time}` to `{end_time}`).
---
### Step 1: Confirm the stockout error and reservation utilization `[Low Risk]`
1. **Check Cloud Audit Logs and GKE operations for stockout or capacity
errors**:
- Run the query inFrom google/skills, Apache-2.0.
Signals
- Stars
- 21,542
- Forks
- 1,821
- Open issues
- 21
- Last commit (this folder)
- Oct 19, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- Version
- 1.0.1
- License
- Apache-2.0
- Repository
- github.com/google/skills
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get gke-ai-troubleshooting-tpu-reservation-stockout running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
gke-ai-troubleshooting-tpu-reservation-stockout skill. Agent Mart. https://agentmart.dev/skills/google-gke-ai-troubleshooting-tpu-reservation-stockout (last updated 2026-10-24)