Question

A node named worker-3 shows status NotReady. You SSH into it and run 'systemctl status kubelet', which reports the kubelet service is active (running). However, the kubelet logs repeatedly show: 'Failed to get container runtime status: rpc error: code = Unavailable desc = connection error: dial unix /run/containerd/containerd.sock: connect: no such file or directory'. What is the most likely root cause and appropriate fix?

Accepted Answer

The containerd service is not running; start and enable it with 'systemctl enable --now containerd', then verify the socket exists

Answer

The kubelet client certificate has expired; rotate it by deleting /var/lib/kubelet/pki and restarting kubelet

Answer

The node has a NoSchedule taint; remove it with 'kubectl taint nodes worker-3 node.kubernetes.io/not-ready-'

Answer

CoreDNS is unreachable from the node; restart the CoreDNS deployment to restore runtime connectivity