A city worker node shows NotReady after a patch window. Investigation finds the kubelet service is stopped. What is the most direct explanation?
Select an answer to reveal the explanation.
Short Explanation
Kubelet is the node’s heartbeat. Stop that service and the control plane soon calls the node NotReady—like a radio that went silent.
Full Explanation
The kubelet reports node status to the API server. If the kubelet process or service is down, heartbeats stop and the node condition becomes NotReady. etcd quorum issues affect the control plane rather than a single worker’s kubelet, CNI pool exhaustion and Deployment replica counts are separate failure modes.