56Nodes go NotReady while pod logs stay innocent. How do kernel failures surface into Kubernetes, and what does Node Problem Detector add?▼mediumNewCloudflareFlipkartRed Hat◆ premiumHeartbeats, conditions and taints are the only vocabulary the control plane understands. NPD translates journald and kernel ring messages into that vocabulary; custom plugins carry your hardware's dialect.Open full answer →
60A pod requesting one GPU stays Pending on a cluster with idle GPU nodes. Debug it.▼hardNewNVIDIAGoogleRed Hat2 replies◆ premiumKubernetes does not see GPUs, it sees an extended resource that something has to advertise. When that advertisement is missing or wrong, the scheduler is behaving correctly and the node is lying.Open full answer →
02A pod has been Pending for ten minutes. Walk me through your diagnosis.▼easy★ EssentialNewFlipkartTCSAccenture2 repliesunlockedThe gentlest scheduling question there is, and it still separates people who read the events from people who guess. Check whether the pod has a node before choosing between scheduling and startup diagnosis.Open full answer →
05A node goes NotReady. What happens to its pods, and on what timeline?▼mediumNewGoogleMetaRed Hat2 repliesunlockedTests whether you know that Kubernetes waits, and for how long. The default timings surprise most candidates, and they explain why a node failure hurts longer than people expect.Open full answer →