Agent skill · google
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
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 needs
About 4k tokens when loaded.
What this skill does
GKE TPU Dynamic Slices Monitoring & Management Monitors the status of TPU Slice custom resources, troubleshoots provisioning failures, validates workload manifests on dynamic slices, and performs cleanups. Prerequisites Cloud Logging enabled for the project. kubectl and gcloud CLIs configured to access the GKE cluster. Diagnostic Workflow Step 0: Context Acquisition & Time Window Definition Gather project, cluster, and slice context using cluster tools or the following parameters: Project ID: {projectid} (e.g., my-gcp-project) Cluster Name: {clustername} (e.g., tpu-cluster) Region/Zone: {location} (e.g., us-central1-a) Slice Name: {slicename} (e.g., test-slice) Issue Time: {timestamp} (Optional; default to the last 30 minutes window [T - 30m] to [T + 30m]) -------------------------------------------------------------------------------- Step 1: Describe the Slice Custom Resource [Low Risk] When asked to inspect, troubleshoot, or check a slice status, immediately execute kubectl describe slice {slicename} using available cluster tools to perform the inspection. Parse the resulting Status.Conditions output against the condition table below to diagnose the exact state and provide concrete recommendations. Command: State & Reason Analysis Analyze the Status.Conditions (especially Type: Ready and its Reason and Status): Lifecycle State / Reason Meaning Recommended Action :--- :--- :--- SliceNotCreated GKE Slice Controller is initializing the slice and performing resource checks. Wait a few minutes and re-check slice status. SliceCreationFailed Prerequisites validation failed (e.g., selected nodes don't exist, nodes are already used by another slice, or the topology doesn't match the number of partitions). Verify selected nodes exist, are unallocated, and topology matches partition count. ACTIVATING GKE is actively forming and provisioning the TPU slice. Monitor node provisioning. ACTIVE The TPU slice is successfully formed and ready to host workloads. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring