gke-ai-troubleshooting-tpu-slice-mig-stuck-updating
Diagnose and resolve GKE TPU Dynamic Slice creation and JobSet scheduling failures blocked by underlying Compute Engine managed instance groups (MIGs) stuck…
Skill by googleOfficial
Chalk Labs
Need help deploying gke-ai-troubleshooting-tpu-slice-mig-stuck-updating?
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-slice-mig-stuck-updating
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-slice-mig-stuck-updating
What's inside
- Skill name
gke-ai-troubleshooting-tpu-slice-mig-stuck-updating- Description
- Diagnose and resolve GKE TPU Dynamic Slice creation and JobSet scheduling failures blocked by underlying Compute Engine managed instance groups (MIGs) stuck in an updating or unstable state (isStable=False). Use when TPU slice creation fails with a SliceCreationFailed status reason, when JobSets remain stuck in pending, or when MIG status reflects isStable=False or versionTarget.isReached=False during TPU slice formation. Don't use for SliceCreationFailed causes unrelated to MIG stability (use gke-ai-troubleshooting-tpu-dynamic-slices-monitoring) or general pod scheduling failures unrelated to TPU slices.
- License
- Apache-2.0
- Metadata
- version: 1.0.1 · category: Containers
- Instructions
- 247 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- attribution.md · references/
SKILL.md (first lines)
# Troubleshoot GKE TPU slice creation blocked by an unstable MIG
This skill helps diagnose GKE TPU Dynamic Slice creation failures and JobSet
scheduling delays when the Compute Engine managed instance groups (MIGs) that
back the TPU node pool aren't stable (`status.isStable: false`).
A `SliceCreationFailed` status reason means that slice creation failed because
prerequisites weren't met (for example, required Compute Engine resources are
missing) or preflight checks failed (see
[Use dynamic slicing with a custom scheduler](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/create-dynamic-slices.md.txt)).
A MIG that is still creating, updating, or repairing instances is one cause to
check. This skill checks the slice status first, then the stability of the
backing MIGs.
## 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-slice-mig-stuck-updating)"`
and append `agent-skills/1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)` to `User-Agent` headers.
## Prerequisites
- **Google Cloud SDK & Tools**:
- For installing and initializing `gcloud` (project selection and
authentication) and enabling the GKE API, follow
[Before you begin](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/create-dynamic-slices.md.txt).
- For installing `kubectl` and configuring cluster credentials, follow the
"Install kubectl", "Install required plugins", and "Store cluster
information for kubectl" sections of
[Install kubectl and configure cluster access](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl.md.txt).
- **API Enablement & Billing**:
- Verify that the project has an active Cloud Billing account.
- Enable APIs: `container.googleapis.com`, `compute.googleapis.com`, and
`logging.googleapis.com`.
- **Required IAM Roles**:
- Logs Viewer (`roles/logging.viewer`): Inspect Cloud Audit Logs for MIG
errors.
- Compute Viewer (`roles/compute.viewer`): Check MIG stability (`isStable`)
and instance progress.
- Kubernetes Engine Viewer (`roles/container.viewer`): Inspect Slice custom
resources (`slices.accelerator.gke.io`), nodes, and cluster operations.
- **Documentation**:
- [Use dynamic slicing with a custom scheduler](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/create-dynamic-slices.md.txt)
(Sections: "Before you begin", "Create a Slice custom resource", "Monitor
the status of the Slice custom resource", "Verify the status of the nodes
and the partitions", "Upgrade your node pools")
- [Install kubectl and configure cluster access](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl.md.txt)
(Sections: "Install kubectl", "Install required plugins", "Store cluster
information for kubectl")
- [Add and manage node pools](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-pools.md.txt)
(Sections: "View node pools in a Standard cluster")
- [View information about MIGs and managed instances](https://docs.cloud.google.com/compute/docs/instance-groups/getting-info-about-migs.md.txt)
(Sections: "Check whether a MIG is stable", "Check the status of managed
instances", "List instance errors")
- [Automatically apply VM configuration updates in a MIG](https://docs.cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups.md.txt)
(Sections: "Verify whether an update rollout is complete")
- [Manually upgrade a cluster's control plane or node pools](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/upgrading-a-cluster.md.txt)
(Sections: "Check node pool upgrade status", "Cancel a node pool upgrade",
"Resume a node pool upgrade", "Roll back a node pool upgrade")
- [Auto-repair nodes](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair.md.txt)
(Sections: "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: "Insufficient quota to satisfy the TPU request", "Insufficient
TPU resources to satisfy the TPU request")
- [REST Resource: projects.locations.clusters.nodePools](https://docs.cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters.nodePools.md.txt)
(Sections: "Resource: NodePool")
- [Schedule dynamic slices with Kueue and TAS](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/use-gke-dynamic-slicing.md.txt)
(Sections: "Monitor the status of the slice")
- [About TPUs in GKE](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/tpus.md.txt)
- [Get support](https://docs.cloud.google.com/kubernetes-engine/docs/getting-support.md.txt)
(Sections: "Before you contact support")
> **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 `[Low Risk]`
Collect the necessary contextual parameters from the user prompt or environment:
- `{project_id}`, `{cluster_name}`, `{location}`, `{nodepool_name}`, and
`{issue_time}`.
- `{mig_name}` and `{zone}`: Name and zone of the managed instance group that
backs `{nodepool_name}`, from the node pool's `instanceGroupUrls` field (see
[View node pools in a Standard cluster](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-pools.md.txt)
and
[Resource: NodePool](https://docs.cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters.nodePools.md.txt)).
If `{nodepool_name}` or `{mig_name}` isn't already known from a failing
`Slice`, find the affected partition, nodes, and backing MIG by following
[Verify the status of the nodes and the partitions](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/create-dynamic-slices.md.txt).
- **Time window**: By default, query a 60-minute window `[{issue_time} - 30m,
{issue_time} + 30m]` (`{start_time}` to `{end_time}`).
---
### Step 1: Detect slice creation failures and MIG errors `[Low Risk]`
1. **Inspect Slice status and partition nodes**: Check the `Slice` custom
resource `Status.Conditions` for a `SliceCreationFailed` status reason and
identify the affected partitions, nodes, and `{mig_name}` by following the
"Monitor the status of the Slice custom resource" and "Verify the status of
the nodes and the partitions" sections of
[Use dynamic slicing with a custom scheduler](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/create-dynamic-slices.md.txt),
and
[Monitor the status of the slice](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/use-gke-dynamic-slicing.md.txt).
2. **Query Cloud Logging for MIG errors**: Once `{mig_name}` is identified (or
by narrowing the results to `{mig_name}` once known), run this Cloud Logging
query to detect errors on the backing instance group manager across
`[{start_time}, {end_time}]`:From 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-slice-mig-stuck-updating 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-slice-mig-stuck-updating skill. Agent Mart. https://agentmart.dev/skills/google-gke-ai-troubleshooting-tpu-slice-mig-stuck-updating (last updated 2026-10-24)