What problem does it solve? When TPU or GPU nodes in GKE stop heartbeating to the control plane, they report NodeStatusUnknown status and pods remain stuck in Terminating, blocking multi-host workload recovery. This Skill systematically identifies whether the failure is caused by kernel panics, hardware errors, preemption, or disabled auto-repair, then guides you to resolution. ## Core Features & Use Cases - Heartbeat Verification: Query Cloud Logging and Monitoring to confirm when the node lost contact with the control plane. - Hardware Diagnosis: Inspect serial port output for kernel panics, NMI lockups, or machine check exceptions. - Auto-Repair Assessment: Verify whether auto-repair is enabled on the node pool and check repair history for failures. - System Event Analysis: Correlate Compute Engine audit logs to identify host errors, preemption, or automatic restarts. - Use Case: A multi-host TPU JobSet workload fails because one node reports NodeStatusUnknown and won't drain. Use this Skill to determine if it's a kernel panic (inspect serial logs), a disabled auto-repair setting (enable it), or insufficient quota (escalate), then apply the appropriate fix. ## Quick Start Provide your GKE cluster name, node pool name, the unresponsive node name, the incident timestamp, and the cluster region or zone, then I will walk you through the five-step diagnostic workflow to identify the root cause and resolution.