← Lab
topoblind
confirmedKubernetesCluster & infrastructureJuly 8, 2026
the question
What does a Kubernetes GPU allocation actually know about the hardware?
what came out
Nothing -- no device identity, no topology, not even a stored utilization figure; the control plane sees a fungible integer count. GPU 'utilization' is derived by summing pod requests, never stored. Four exact API-state facts on a 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/topoblind