Kubernetes node NotReady (Kubelet stopped posting node status)
The control plane hasn’t heard from a node’s kubelet, or the kubelet reports a problem — pods there stop being scheduled and are later evicted.
Kubelet stopped posting node statusnode is not readynetwork plugin is not ready: cni config uninitialized Meaning
NotReady comes from the kubelet being down, the container runtime failing, the CNI plugin not ready (“network plugin is not ready: cni config uninitialized”), the node out of disk/memory/PIDs, or the network to the API server breaking.
Common causes
- kubelet or containerd stopped/crashing
- CNI not installed or its pod failing
- Node resource pressure (disk, memory, PID)
- Expired kubelet certificates
- Network partition to the control plane
⚡ Quick fix
- kubectl describe node → Conditions and events
- On the node: systemctl status kubelet containerd; journalctl -u kubelet
- Check CNI pods in kube-system
Detailed fix by platform
Linux
- bash
sudo systemctl status kubelet containerd sudo journalctl -u kubelet --since '15 min ago' | tail -50
Kubernetes
- bash
kubectl describe node worker-2 | sed -n '/Conditions/,/Addresses/p' kubectl get pods -n kube-system -o wide | grep worker-2
How to diagnose
- Conditions — Ready reason/message
- Kubelet — Service running, logs
- CNI — Network plugin pods on that node
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Kubernetes
- cannot re-use a name that is still in use Error: INSTALLATION FAILED: cannot re-use a name that is still in use
- error converting YAML to JSON error converting YAML to JSON: yaml: line 12: did not find expected key
- unknown field strict decoding error: unknown field "spec.template.spec.containers[0].ports[0].protocl"
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026