What problem does it solve?
AIPerf benchmarks running on Kubernetes can get stuck Pending, crash-loop, OOM-kill, stall mid-run, or fail with opaque errors, and finding the root cause requires knowing which of the many CR status fields, pod containers, and log streams actually matter for each failure phase.
Core Features & Use Cases
- Phase-based triage routing: Classify an AIPerfJob or AIPerfSweep by
status.phase (Pending, Queued, Initializing, Running, Failed) and follow the matching diagnostic branch with kubectl and aiperf kube debug commands.
- Failure pattern tables: Map
status.error strings, scheduling messages, exit codes, and error-rate bands to concrete root causes and fixes, including the nineteen immutable spec fields that force delete-and-recreate instead of patching.
- Use Case: A benchmark shows
Running but requestsCompleted is flat. The skill directs you to test endpoint reachability from inside the cluster, grep worker logs for the credit-return channel warning, and check for CPU starvation of the records-manager before blaming the endpoint.
Quick Start
Ask the assistant to triage why your AIPerfJob named my-benchmark in namespace aiperf is stuck and not making progress.