A Kubernetes worker node, named wk8s-node-0 is in state NotReady. Investigate why this is the case, and perform any appropriate steps to bring the node to a Ready state, ensuring that any changes…

Question

Explanation

This CKA exam simulation tests your ability to troubleshoot a Kubernetes worker node in a NotReady state by diagnosing and restarting the kubelet service, then ensuring it persists across reboots.

Approach. The most common cause of a node entering NotReady state is a stopped or failed kubelet service - the primary node agent that communicates with the control plane. The correct procedure is: (1) SSH into the node with 'ssh wk8s-node-0' and escalate with 'sudo -i'; (2) check the kubelet status with 'systemctl status kubelet' and review logs via 'journalctl -u kubelet --no-pager | tail -20'; (3) start the service with 'systemctl start kubelet'; (4) make the change permanent (survive reboots) with 'systemctl enable kubelet'. After returning to the control plane, confirm recovery with 'kubectl get nodes' and verify wk8s-node-0 shows Ready.

Concept tested. Kubernetes node troubleshooting - specifically diagnosing NotReady state caused by a stopped kubelet, using systemctl to start and enable the kubelet service for persistent recovery. This is a core CKA domain: Cluster Maintenance / Troubleshooting.

Reference. https://kubernetes.io/docs/tasks/debug/debug-cluster/#worker-nodes

No community discussion yet for this question.