K8s Troubleshooting — Node NotReady (Node Status)

K8s Troubleshooting handbook

Note, full K8s troubleshooting mind map is available at: “K8s Troubleshooting MindMap”

Node in NotReady Status

In K8s, when a node is in the NotReady status, it means that the node is currently unavailable or unhealthy, and it cannot accept new workloads or schedule new pods.

For example:

$ kubectl get nodes
NAME          STATUS     ROLES     AGE    VERSION
k8s-master    Ready      master    10d    v1.24.0
k8s-worker1   NotReady   worker    10d    v1.24.0
k8s-worker2   Ready      worker    10d    v1.24.0

In this example, the k8s-worker1 node is in NotReady status. To investigate the cause of the NotReady status, you can use the kubectl describe node command:

$ kubectl describe node k8s-worker1

The output will look similar to:

Name:               k8s-worker1
Roles:              worker
...
Status:             NotReady
...
Conditions:
  Type              Status    LastHeartbeatTime                 LastTransitionTime                Reason                Message
  ----              ------    -----------------                 ------------------                ------                -------
  Ready…