Kubernetes Node Not Ready: Troubleshooting Guide

Symptom

kubectl get nodes shows NotReady; pods scheduled elsewhere.

Root cause

The kubelet is down or the node is out of disk/pid pressure.

Fix, in order

1. Check kubelet on the nodesystemctl status kubelet
2. Look at node conditionskubectl describe node <node> | grep -A12 Conditions
3. Free disk: evicted images and logs firstjournalctl -u kubelet -n 50 --no-pager

Prevent it coming back

Alert on DiskPressure/PIDPressure conditions before they flip to NotReady.

Deep-dive article

Full walkthrough: Kubernetes Node Not Ready: Troubleshooting Guide on the NinjaOps blog.

Run it on clean infra

Spinning up a fresh box to reproduce or escape this error?

Servers with headroom

Related

Cloud & DevOps tool comparisons · Hardware build guides

NinjaOps publishes free engineering guides. Some outbound links are affiliate links: they cost you nothing and support the site.

Last reviewed 2026-10-02 · NinjaOps SEO grid · DevOps blog