Assume node worker2 is not currently available. Ensure the appropriate service is started so that the node becomes Ready again.
kubectl get nodes
Example output:
NAME STATUS cp1 Ready worker1 Ready worker2 NotReady
ssh worker2
The kubelet is responsible for communicating with the Kubernetes control plane. If it is stopped, the node usually shows as NotReady.
sudo systemctl status kubelet
Possible output:
Active: inactive (dead)
sudo systemctl start kubelet
Verify that it started successfully:
sudo systemctl status kubelet
Expected output:
Active: active (running)
Optional but considered good practice:
sudo systemctl enable kubelet
Return to the control plane node and check the status:
kubectl get nodes
Expected output:
NAME STATUS cp1 Ready worker1 Ready worker2 Ready
If worker2 is still NotReady after starting kubelet, investigate further.
sudo journalctl -u kubelet -xe
sudo systemctl status containerd
sudo systemctl start containerd
kubectl get nodes ssh worker2 sudo systemctl start kubelet exit kubectl get nodes
sudo systemctl status kubelet
Add your own observations, troubleshooting notes, and screenshots.