Gke AI troubleshooting node unresponsive timeout vs Gke AI troubleshooting tpu partition overlap
Gke AI troubleshooting node unresponsive timeout is an open-source agent skill for cloud and infrastructure. Gke AI troubleshooting tpu partition overlap is an open-source agent skill for cloud and infrastructure.
- Gke AI troubleshooting node unresponsive timeout is best for find out why a gke tpu node has been notready for an hour.
- Gke AI troubleshooting tpu partition overlap is best for diagnose why a tpu slice in gke stays in slicecreationfailed.
- What it is
- Gke AI troubleshooting node unresponsive timeout is an open-source agent skill for cloud and infrastructure.Gke AI troubleshooting tpu partition overlap is an open-source agent skill for cloud and infrastructure.
- Best for
- Find out why a GKE TPU node has been NotReady for an hourDiagnose why a TPU slice in GKE stays in SliceCreationFailed
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- GitHub stars
- 24.4K24.4K
- Last commit
- Nov 2026Nov 2026
- License
- Apache-2.0Apache-2.0
- Open source
- Good for
- Find out why a GKE TPU node has been NotReady for an hour; Check whether a GPU node was preempted or hit a host error; Review serial console output for a kernel panic on a stuck nodeDiagnose why a TPU slice in GKE stays in SliceCreationFailed; Find which other slice is holding the nodes my TPU partitions need; Check which TPU partitions are healthy and free for a new dynamic slice
What Gke AI troubleshooting node unresponsive timeout does
Node condition verification
Confirms whether the Ready condition is Unknown with NodeStatusUnknown, using Kubernetes status and Cloud Monitoring metrics.
Serial output kernel panic check
Reviews VM serial port output for kernel panic and hardware crash patterns such as machine check or hung task messages.
Auto-repair status review
Checks whether node auto-repair is enabled on the node pool and inspects recent repair events and failure reasons.
Compute Engine event analysis
Looks through audit log events such as host errors, preemptions and automatic restarts to explain why a VM stopped.
Read-only remediation guidance
Keeps diagnostics non-destructive and points the user to documented repair steps, with warnings against force-deleting pods.
What Gke AI troubleshooting tpu partition overlap does
Confirm SliceCreationFailed status
Checks the Ready condition reason and records partition IDs, topology and labels from the Slice resource.
Rule out other causes
Checks for missing nodes or a mismatch between topology and partition count before concluding overlap.
Map partition usage on nodes
Reads partition ID and state labels across all slice shapes to see which partitions are available.
Find conflicting slices
Identifies other slices and JobSets that use the same nodes, using the Slice resources and Cloud Monitoring metrics.
Guided resolution options
Suggests Kueue and TAS scheduling, slice reuse settings, retry annotations or escalation to support.
Read-only safety rules
Limits the agent to read-only commands and leaves any cluster changes to the user.
Gke AI troubleshooting node unresponsive timeout vs Gke AI troubleshooting tpu partition overlap: questions
Is Gke AI troubleshooting node unresponsive timeout or Gke AI troubleshooting tpu partition overlap cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Gke AI troubleshooting node unresponsive timeout and Gke AI troubleshooting tpu partition overlap?
Gke AI troubleshooting node unresponsive timeout is an open-source agent skill for cloud and infrastructure. Gke AI troubleshooting tpu partition overlap is an open-source agent skill for cloud and infrastructure.
