← Lab
gangdeadlock
confirmedKubernetesCluster & infrastructureJuly 8, 2026
the question
Can two competing multi-pod GPU gangs deadlock the default Kubernetes scheduler?
what came out
Yes -- the scheduling atom is one Pod, so two gangs in a 2/2 split strand all 4 GPUs with 0 gangs runnable, and the default scheduler neither prevents nor breaks it. One atomic multi-GPU pod per job is structurally immune. Real cluster, independently verified.
method & receipts
- Result: confirmed
- Pre-registered — the prediction was written down and committed before the run.
- Reproducible — one script re-runs the whole thing from scratch.
- Independently reviewed — an adversarial review pass, kept in the repo.
- Machine-readable claims — every reported number, in a checkable file.
- Tested — a correctness/benchmark suite ships alongside the code.
→ read the code and re-run it
github.com/v-code01/gangdeadlock