
Diagnoses GKE TPU slice creation stalls caused by unstable Compute Engine MIGs
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure


Diagnoses GKE TPU slice creation stalls caused by unstable Compute Engine MIGs

Diagnoses GKE TPU SliceCreationFailed errors caused by overlapping partitions or nodes

Diagnoses AKS GPU and KAITO incidents using read-only cluster evidence

Finds AKS scheduling, bin-packing, node scaling and storage cost inefficiencies

Guides agents through diagnosing GKE TPU multi-slice training hangs using MXLA analyzer

Diagnoses GKE TPU VMs stuck in Compute Engine REPAIRING state and routes recovery

Diagnoses GKE TPU training throughput drops using ML Diagnostics and Cloud Monitoring

Diagnoses GKE TPU node pool stockouts caused by unhealthy pools holding reservation slots

Monitors GKE TPU nodes, node pools and workloads using system metrics and PromQL

Diagnoses and mitigates GKE GPU and TPU node disruptions from host maintenance events

Diagnoses GKE TPU and GPU nodes stuck NotReady after kernel panics or hardware lockups

Diagnoses vbar_control_agent OOMs and TPU v6e device failures on GKE clusters

Diagnoses GKE persistent storage failures like attach, mount, pressure and expansion

Diagnoses failing GKE workloads from pod status, events, logs and network checks
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.
Yes. Gke AI troubleshooting tpu slice mig stuck updating, Gke AI troubleshooting tpu partition overlap, Aks GPU inference have a free or open-source option.