Gke AI Troubleshooting Tpu Reservation Stockout
GoogleOfficialPublished by Google
- Skill
- Review and audit
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a diagnostic workflow to troubleshoot GKE TPU node pool creation or scale-up failures triggered by GCE_STOCKOUT or ZONE_RESOURCE_POOL_EXHAUSTED errors. It specifically addresses scenarios where existing, unhealthy TPU node pools with auto-repair disabled continue to consume reserved TPU capacity, preventing new node pools from scaling. The skill guides users through verifying reservation utilization, identifying the specific node pools holding the capacity, and determining the appropriate remediation steps to free up resources.
What it does
- Confirms GKE TPU reservation stockout errors via audit logs and operation history.
- Checks Compute Engine reservation utilization to identify consumed capacity.
- Maps VMs consuming reservation slots to specific GKE clusters and node pools.
- Verifies the status of node auto-repair on suspected leaking node pools.
- Provides guidance on safely freeing reservation capacity for new node pool deployments.
When to use it
- When GKE TPU node pool creation fails with GCE_STOCKOUT or ZONE_RESOURCE_POOL_EXHAUSTED.
- When you suspect existing, unhealthy TPU node pools are holding onto reserved capacity.
- When you need to verify if node auto-repair is correctly configured for TPU workloads.
- When you need to identify which specific node pools are consuming your TPU reservation.
Advantages
- Systematic approach to identifying resource leaks in GKE TPU reservations.
- Helps distinguish between genuine resource exhaustion and capacity held by stale nodes.
- Provides clear, actionable steps for resolving capacity conflicts.
- Adheres to safe operational practices by prioritizing read-only diagnostics.
Usage examples
- “My GKE TPU node pool creation is failing with GCE_STOCKOUT. How do I check if my reservation is full?”
- The agent will guide you through checking the reservation utilization and identifying which node pools are consuming the slots.
- “How can I tell if an unhealthy node pool is preventing my new TPU node pool from scaling up?”
- The agent will help you correlate the failing operation with existing node pool health and reservation consumption metrics.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/gke-ai-troubleshooting-tpu-reservation-stockout/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip gke-ai-troubleshooting-tpu-reservation-stockout.zip -d .agents/skills
Documentation by Google
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,
the reservation must have sufficient available TPU chips at the time of node
pool creation, and per
Multi-host TPU slice node pools,
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)
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. 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.inUseCountvsspecificReservation.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, andmonitoring.googleapis.com.
CLI & Authentication Setup:
Install Google Cloud SDK (
gcloud) andkubectl: 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).
Reference Documentation:
Auto-repair nodes (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 (Sections: "Issue: Node pool creation fails due to insufficient resources")
Troubleshoot TPUs in GKE (Sections: "How GKE handles capacity issues", "Insufficient TPU resources to satisfy the TPU request")
About TPUs in GKE (Sections: "Multi-host TPU slice node pools")
Consuming reserved zonal resources (Sections: "Consuming a specific shared reservation")
About reservations (Sections: "How reservations work")
View reservations or future reservation requests (Sections: "Limitations", "View reservations", "Consumable instances in a reservation", "View a list of instances that are consuming a reservation")
Organize resources using labels (Sections: "View labels")
Create and manage cluster and node pool labels (Sections: "Automatically applied labels")
Deploy TPU workloads in GKE Standard (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 (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),{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]
Check Cloud Audit Logs and GKE operations for stockout or capacity errors:
Run the query in Issue: Node pool creation fails due to insufficient resources across
[{start_time}, {end_time}]and look for the documented error messages, such asZONE_RESOURCE_POOL_EXHAUSTEDorZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS.Per Insufficient TPU resources to satisfy the TPU request, TPU errors can also contain
GCE_STOCKOUT.Per How GKE handles capacity issues, GKE sometimes queues a TPU node pool creation request instead of failing it immediately, surfacing a
... cannot be created ... due to lack of capacitymessage instead ofGCE_STOCKOUT. List the node pool creation operation withgcloud container operations list(--filter="operationType=CREATE_NODE_POOL").
Check Compute Engine reservation utilization:
Per Limitations, query shared reservations in the owner project where they were created (
{reservation_project_id}).Follow the View reservations section to run
gcloud compute reservations describe {reservation_name} --zone={zone} --project={reservation_project_id}orgcloud compute reservations list --project={reservation_project_id}, and comparespecificReservation.inUseCountagainstspecificReservation.count.
Interpret the results
Don't suggest deleting any node pool until you have identified which existing VMs and node pools hold the reserved capacity (Step 2).
Stockout confirmed: Per Ensure reservation availability and Multi-host TPU slice node pools, if GKE can't deploy one node in a multi-host slice, no nodes in the slice are deployed. If a stockout or lack-of-capacity message is present and the free slots (
specificReservation.count - specificReservation.inUseCount; see Consumable instances in a reservation) are fewer than the number of nodes that{failing_nodepool_name}needs, proceed to Step 2.
Step 2: Find which VMs and node pools hold the reservation [Low Risk]
Check which VMs are consuming
{reservation_name}:Per How reservations work, a specifically targeted reservation can be used by VMs in the reservation's project (
{reservation_project_id}) or, for a shared reservation, in any project that it's shared with.Follow View a list of instances that are consuming a reservation to list the VMs that use
{reservation_name}.Follow View labels to view each VM's labels, and check the GKE labels in Automatically applied labels (
goog-k8s-cluster-name,goog-k8s-cluster-location, andgoog-k8s-node-pool-name) to find each VM's cluster and node pool.
Check node readiness in
{cluster_name}:Query the Cloud Monitoring metric
kubernetes_io:node_status_condition(monitored_resource="k8s_node",cluster_name="{cluster_name}",condition="Ready") described in Monitor health metrics for TPU nodes and node pools. Thestatuslabel value isTrue,False, orUnknown(capitalized); usestatus!="True"to find nodes whoseReadycondition isFalseorUnknown.List TPU nodes and their node pool labels with
kubectl get nodes -l cloud.google.com/gke-tpu-accelerator -L cloud.google.com/gke-nodepool.
Exclude the failing node pool: Leave
{failing_nodepool_name}out of the unhealthy list. It's the node pool that couldn't get capacity, not the one holding it.
Interpret the results
VMs outside
{cluster_name}: If some of the VMs consuming{reservation_name}aren't nodes in{cluster_name}(for example, their labels show another GKE cluster or they are Compute Engine VMs without GKE labels), tell the user which VMs or other clusters hold those reservation slots.Fewer listed VMs than
specificReservation.inUseCount: Per View a list of instances that are consuming a reservation, the list only includes VMs in one project. If the list has fewer VMs thanspecificReservation.inUseCount, tell the user that VMs in other projects that share{reservation_name}are consuming the remaining slots.Unhealthy node pool in
{cluster_name}({leaking_nodepool_name}): If the VMs consuming{reservation_name}belong to an existingNotReadynode pool in{cluster_name}({leaking_nodepool_name}), proceed to Step 3.Healthy reservation (rule out a leak): If the reserved slots are held by healthy, in-use node pools, there is no leak. Explain that healthy node pools hold the reserved slots, so too few slots are free for
{failing_nodepool_name}. Tell the user not to delete or restart those healthy node pools, and point the user to the consumption options in Insufficient TPU resources to satisfy the TPU request.
Step 3: Verify node auto-repair on the leaking node pool [Low Risk]
Follow
Verify node auto-repair is enabled for a Standard node pool
for {leaking_nodepool_name}:
Auto-repair is disabled (
management.autoRepair: false): GKE doesn't repair theNotReadynodes in{leaking_nodepool_name}. Their running VMs keep counting towardspecificReservation.inUseCountin{reservation_name}, so{failing_nodepool_name}can't get reserved capacity. Proceed to Step 4.Auto-repair is enabled (
management.autoRepair: true), but nodes are stillNotReady:Check whether the nodes have been
NotReadyfor less than the repair time threshold (approximately 10 minutes), per Repair criteria.Check the repair status and the failure reason in the operation history, per Configure auto repair for TPU slice nodes and Get information about recent automated repair events.
Step 4: Recover or release the reservation capacity [High Risk]
Guardrail: Don't modify GKE-managed instance groups or VMs directly through Compute Engine. Manage node pools through GKE. Never delete healthy node pools that run active jobs.
If the user wants to repair
{leaking_nodepool_name}in place, enable node auto-repair (doesn't free slots for{failing_nodepool_name}):Per Node repair process, GKE drains and re-creates an unhealthy node.
Per Node auto repair in TPU slice nodes and Configure auto repair for TPU slice nodes, GKE re-creates the entire multi-host TPU slice node pool when a node in it needs repair. The re-created VMs still consume
{reservation_name}, sospecificReservation.inUseCountdoesn't drop: enabling auto-repair makes the nodes in{leaking_nodepool_name}healthy again, but{failing_nodepool_name}still can't get their slots.Link the user to Enable auto-repair for an existing Standard node pool to turn on auto-repair for
{leaking_nodepool_name}.
If
{leaking_nodepool_name}is stale or the user wants to free its slots for{failing_nodepool_name}, delete it through GKE: Link the user to Delete a node pool to delete{leaking_nodepool_name}, which frees the reserved slots its VMs use.After the user deletes
{leaking_nodepool_name}, verify that enough reservation slots are free: Follow View reservations to rungcloud compute reservations describe {reservation_name} --zone={zone} --project={reservation_project_id}and confirm thatspecificReservation.inUseCountdrops so the free slots (specificReservation.count - specificReservation.inUseCount) are at least the number of nodes that{failing_nodepool_name}needs before retrying{failing_nodepool_name}.
Files
- ATTRIBUTION.mdAdded by AutoGineer912 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md17.2 KiB
- references/attribution.md1.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/gke-ai-troubleshooting-tpu-reservation-stockout · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download gke-ai-troubleshooting-tpu-reservation-stockout.zip