kubernetes node_error ai_generated partial

Node condition: NotReady

ID: kubernetes/node-not-ready

Also available as: JSON · Markdown
78%Fix Rate
85%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —

Root Cause

Kubernetes node is not healthy. Kubelet, container runtime, or networking issue.

generic

Workarounds

  1. 92% success Check kubelet status: systemctl status kubelet on the node 
    systemctl status kubelet on the node

    Sources: https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/

  2. 90% success Check node conditions: kubectl describe node <name> for detailed status 
    kubectl describe node

    Sources: https://kubernetes.io/docs/concepts/architecture/nodes/#condition

  3. 85% success Common causes: disk pressure, memory pressure, PID pressure, or container runtime down 
    disk pressure, memory pressure, PID pressure, or container runtime down

    Sources: https://kubernetes.io/docs/concepts/architecture/nodes/#condition

Dead Ends

Common approaches that don't work:

  1. Delete the node and readd it 65% fail

    May lose workloads that aren't replicated

  2. Cordon and ignore 50% fail

    Doesn't fix the issue — workloads won't be scheduled there

Error Chain

Frequently confused with: