Worker NotReady: kubelet stopped
Scenario cka-trb-001 · about 7 minutes · 7 points · 3 grader checks
A worker node reports NotReady; diagnose and restore it without recreating the node.
- troubleshooting
- node
- kubelet
- notready
What you will practise
- Diagnose a NotReady node
- Inspect and restart node services with systemctl
- Repair a node in place rather than recreating it
Start this lab
With the CLI installed and signed in, this command provisions a two nodes cluster on your Mac, applies the scenario setup and prints the task below.
goldenkube start cka-trb-001Task
The task text exactly as the CLI shows it. Solve it on the cluster, then run goldenkube submit.
Requirements and details
- Certification
- CKA · Certified Kubernetes Administrator
- Domain
- Troubleshooting
- Difficulty
- Medium
- Cluster topology
- Two nodes
- Cluster features
- None beyond the base cluster
- Recommended time
- 7 minutes
- Points
- 7
- Grader checks
- 3
- Kubernetes version
- 1.37
- Minimum CLI version
- 0.1.0
- Scenario version
- 1
- Published
Grading runs locally: 3 state checks read your cluster when you submit; the scenario passes when every check passes. Hints, the reference solution and the check definitions are available only inside the CLI, not on this page.
More Troubleshooting labs
Worker NotReady: kubelet fails to start
The kubelet on a worker refuses to start; find the misconfiguration and fix it on the node.
Two nodes · ~8 min · 7 points
- troubleshooting
- node
- kubelet
- systemd
- configuration
goldenkube start cka-trb-002
kube-apiserver static pod broken
kubectl cannot reach the cluster; repair the API server from the control plane node.
Single node · ~8 min · 8 points
- troubleshooting
- kube-apiserver
- static-pod
- control-plane
- crictl
goldenkube start cka-trb-003
Worker NotReady: container runtime down
A worker is NotReady although its kubelet runs; find the underlying runtime problem and fix it.
Two nodes · ~6 min · 6 points
- troubleshooting
- node
- containerd
- cri
- kubelet
goldenkube start cka-trb-004
Cluster DNS down
Service name resolution has stopped working; investigate and restore the cluster DNS component.
Two nodes · ~5 min · 5 points
- troubleshooting
- coredns
- dns
- kube-system
goldenkube start cka-trb-005
Independent community project, not affiliated with or endorsed by CNCF or The Linux Foundation. Lab results are practice feedback, not an exam score.