# Gke AI troubleshooting tpu dynamic slices monitoring

> Gke AI troubleshooting tpu dynamic slices monitoring is an open-source agent skill for cloud and infrastructure. Inspect, troubleshoot and validate GKE TPU dynamic slice resources and workloads. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/google/skills/tree/main/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
- **Repository:** https://github.com/google/skills
- **GitHub stars:** 24,379
- **License:** Apache-2.0
- **Skill name:** gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
- **Collection:** https://github.com/google/skills
- **Categories:** [cloud and infrastructure](https://ai-powered.com/categories/cloud-and-infrastructure)
- **Listing updated:** 2026-11-18

## About

This skill helps an agent check the lifecycle state of GKE TPU Dynamic Slice custom resources and interpret their status conditions against a reference table of states such as provisioning, active, degraded and failed. When a slice fails to provision, it walks through a checklist covering node existence and allocation, topology alignment with partition count, and reservation block consistency.

It also reviews workload manifests meant for dynamic slices, checking the required annotations and node selectors for single-slice pods and the extra JobSet exclusive-topology annotation for multi-slice deployments. For slices stuck in deletion, it describes removing finalizers with a JSON patch and warns about possibly orphaned VM, network or accelerator resources. Disabling the slice controller and cleaning up CRDs and node labels is also covered.

The workflow relies on kubectl and gcloud configured against the target GKE cluster, with Cloud Logging enabled on the project. Destructive steps such as patching finalizers or disabling the controller are gated behind explicit user confirmation.

## When your agent uses it

> Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use for generic GKE cluster node pool creation or standard non-TPU workload management (use gke-basics or gke-cluster-creation instead).

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Runs shell scripts](https://github.com/google/skills/tree/HEAD/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring)
- [No network calls found in its scripts](https://github.com/google/skills/tree/HEAD/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring)
- [License: Apache-2.0](https://github.com/google/skills/tree/HEAD/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring)

## Features

- **Slice state analysis:** Reads slice status conditions and maps lifecycle states and reasons to likely causes and next actions.
- **Provisioning failure checklist:** Verifies node existence, allocation, topology match and reservation block alignment when slices fail.
- **Single-slice manifest validation:** Checks pod template annotations and node selectors needed to target a dynamic TPU slice.
- **Multi-slice JobSet validation:** Confirms JobSet exclusive-topology annotation and TPU selectors for multi-slice workloads.
- **Stuck finalizer removal:** Describes a guarded JSON patch to clear finalizers on slices stuck in deletion, with risk warnings.
- **Slice controller teardown:** Outlines disabling the slice controller, removing the CRD and clearing TPU slice node labels.

## Good for

- Check why a TPU slice is stuck in provisioning or shows a failed state
- Validate a single-slice TPU training pod manifest before deploying it
- Verify a multi-slice JobSet manifest targets TPU slices correctly
- Clean up a TPU slice stuck in deactivating after confirming the risks
- Disable GKE dynamic slicing on a cluster and remove leftover slice labels

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/google/skills.git --path skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
```

Or copy the folder to `~/.gemini/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.copilot/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/google/skills.git
```

Then copy `skills/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring` into your agent's skills folder as `gke-ai-troubleshooting-tpu-dynamic-slices-monitoring`. Agents that support SKILL.md read one folder per skill.

## FAQ

### What tools does it need?

It needs kubectl and gcloud CLIs configured to access the GKE cluster, and Cloud Logging enabled for the project.

### Does it change my cluster without asking?

No. Patching finalizers and disabling the slice controller are high-risk and require explicit user confirmation before execution.

### When does it apply?

It applies to GKE TPU Dynamic Slices troubleshooting and manifest checks. It advises using gke-basics or gke-cluster-creation for general node pool creation or non-TPU workloads.

### What license is it released under?

The skill is in the google/skills repository, which is licensed under Apache-2.0.

### How do I install Gke AI troubleshooting tpu dynamic slices monitoring in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring to use it in all your projects, or to .claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring in one project.

### Does Gke AI troubleshooting tpu dynamic slices monitoring run scripts?

Yes. It runs shell scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Gke AI troubleshooting tpu dynamic slices monitoring?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

### What are the best alternatives to Gke AI troubleshooting tpu dynamic slices monitoring?

The closest alternatives to Gke AI troubleshooting tpu dynamic slices monitoring are Gke AI troubleshooting tpu slice mig stuck updating, Gke AI troubleshooting tpu partition overlap, Aks GPU inference, Aks cost optimization and Gke AI troubleshooting tpu mxla hang.

## Where this comes from

- Description: from the skill's own SKILL.md.

## Alternatives

- [Gke AI troubleshooting tpu slice mig stuck updating](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-slice-mig-stuck-updating): Gke AI troubleshooting tpu slice mig stuck updating is an open-source agent skill for cloud and infrastructure.
- [Gke AI troubleshooting tpu partition overlap](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-partition-overlap): Gke AI troubleshooting tpu partition overlap is an open-source agent skill for cloud and infrastructure.
- [Aks GPU inference](https://ai-powered.com/skills/aks-gpu-inference): Aks GPU inference is an open-source agent skill for cloud and infrastructure.
- [Aks cost optimization](https://ai-powered.com/skills/aks-cost-optimization): Aks cost optimization is an open-source agent skill for cloud and infrastructure.
- [Gke AI troubleshooting tpu mxla hang](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-mxla-hang): Gke AI troubleshooting tpu mxla hang is an open-source agent skill for cloud and infrastructure.
- [Gke AI troubleshooting tpu vm repair stuck](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-vm-repair-stuck): Gke AI troubleshooting tpu vm repair stuck is an open-source agent skill for cloud and infrastructure.
- [Gke AI troubleshooting tpu performance degradation](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-performance-degradation): Gke AI troubleshooting tpu performance degradation is an open-source agent skill for cloud and infrastructure.
- [Gke AI troubleshooting tpu reservation stockout](https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-reservation-stockout): Gke AI troubleshooting tpu reservation stockout is an open-source agent skill for cloud and infrastructure.

---
Source: https://ai-powered.com/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
