26Walk me through what the kubelet does between PodScheduled and a running container. Why do nodes flap NotReady while pods keep serving?▼expert★ EssentialNewGoogleRed HatDatadog◆ premiumThe kubelet is a local reconcile loop with its own event stream, probe workers and eviction brain. Staff-level candidates can narrate it and explain why Ready status can reflect either reported health failure or missing heartbeats.Open full answer →
45Off-peak, the autoscaler removes nodes and our Spark driver got evicted mid-run. How does scale-down choose its victims?▼mediumNewAmazon & AWSLinkedInAtlassian◆ premiumScale-downers mark a node removable only when every pod on it can leave safely. Your batch workload died because nothing marked it special. The mechanism is a filter cascade, and the fix is priorities, PDBs and annotations.Open full answer →
46Worker nodes slowly fill their disks until DiskPressure appears. How does the kubelet decide what to clean up?▼easyNewDatadogUberNVIDIA◆ premiumTwo cleanup mechanisms hide behind one taint: image garbage collection removes unreferenced images by LRU at threshold crossings, while eviction kills pods. Candidates who conflate them fail this question quietly.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 →