3οΈβ£ Still no heartbeat after 5 min (pod-eviction-timeout) β pods get evicted
Root causes I check first:
β Disk full (DiskPressure)
β kubelet/containerd crashed
β Node β API server network broken
β Clock skew / expired kubelet cert
β Underlying EC2 instance impaired
#devops
What does "Node NotReady" actually mean?
It's not the node dying β it's the control plane not hearing from it.
Here's the chain:
1οΈβ£ kubelet sends heartbeats to API server every ~10s
2οΈβ£ No heartbeat within 40s (node-monitor-grace-period) β Ready flips to Unknown
5/ Check certificates
kubeadm certs check-expiration
6/ Verify critical pods rescheduled
kubectl get pods -o wide
Bonus: K8s auto adds NotReady taint
β Pods evict after 5 mins
β Reschedule on healthy nodes automatically
Save this for your next interview π₯
#Kubernetes#DevOps
Got this in a K8s interview π
"Node is NotReady at 2AM,
3 critical pods are down.
What do you do?"
Here's how to answer it π§΅
1/ Check node status
kubectl get nodes
kubectl describe node <name>
2/ Check Conditions
β MemoryPressure β free -h