NodeNotReady
The node stopped reporting healthy, so pods on it are disrupted.
The kubelet is down, the node is out of resources, or the network path to the API server broke. Pods show this as a taint or a NodeNotReady event.
Commands to start with
- kubectl get nodes
- kubectl describe node NODE
Explain a NodeNotReady paste
Output
The result shows up here. Your input is not written to the log.
Questions
›Will pods move by themselves?
Not immediately. The controller waits out the pod eviction timeout, then reschedules Deployments and StatefulSets.
›What should I check on the node?
kubelet status, disk pressure, and whether the node can reach the API server. The describe output lists the conditions.