← Lab
gpuqos
confirmedKubernetesCluster & infrastructureJuly 9, 2026
the question
What QoS class does a GPU-only pod get on Kubernetes?
what came out
BestEffort -- with the max kernel oom_score_adj (1000), making it the first OOM victim under memory pressure, because Kubernetes computes QoS from cpu/memory alone and ignores the GPU. Two independent signals (API qosClass + kernel oom_score_adj) on a real cluster: the scarce-GPU holder dies first.
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/gpuqos