There can be a lot of reasons why a worker node is not ready. By looking at the node description, it’s not ready and network is not available.
k get nodes
node01 NotReady <none>
k describe node01
...
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Wed, 08 Oct 2025 12:33:43 +0000 Wed, 08 Oct 2025 12:33:43 +0000 FlannelIsUp Flannel is running on this node
MemoryPressure Unknown Wed, 08 Oct 2025 12:34:08 +0000 Wed, 08 Oct 2025 12:36:04 +0000 NodeStatusUnknown Kubelet stopped posting node status.
DiskPressure Unknown Wed, 08 Oct 2025 12:34:08 +0000 Wed, 08 Oct 2025 12:36:04 +0000 NodeStatusUnknown Kubelet stopped posting node status.
PIDPressure Unknown Wed, 08 Oct 2025 12:34:08 +0000 Wed, 08 Oct 2025 12:36:04 +0000 NodeStatusUnknown Kubelet stopped posting node status.
Ready Unknown Wed, 08 Oct 2025 12:34:08 +0000 Wed, 08 Oct 2025 12:36:04 +0000 NodeStatusUnknown Kubelet stopped posting node status.The common troubleshooting steps are:
- Check if containerd is running:
systemctl status containerd - Check if kubelet is running:
systemctl status kubelet - If kubelet is inactive, start it with
systemctl start kubelet