01Walk me through what happens when a pod asks Kubernetes for four GPUs, from the manifest to the container seeing them.▼easy★ EssentialNewCoreWeaveNebiusModal4 repliesunlockedThe four layers between `nvidia.com/gpu: 4` and a container that can run CUDA, the one failure each layer produces, the stranded-GPU arithmetic the integer model causes, and why Dynamic Resource Allocation replaces the count with a claim.Open full answer →
08Here is a Kubernetes GPU node. Pods requesting nvidia.com/gpu stay Pending. Fix it in front of me and narrate what you check.▼medium★ EssentialNewNebiusCoreWeave4 repliesunlockedA node with eight healthy H100s that Kubernetes thinks has none. The layered check from kernel driver to container toolkit to device plugin to taints and allocatable, in the order that isolates the fault fastest, with the log lines each layer prints when it is the one that broke.Open full answer →