kubeadm error – kubelet isn’t running or healthy and connection refused

Spread the Knowledge

Errors Headlines

  • Initial timeout of 40s passed
  • dial tcp [::1]:10248: connect: connection refused
  • failed with error: Get http://localhost:10248/healthz
  • The kubelet is not running


If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
– ‘systemctl status kubelet’
– ‘journalctl -xeu kubelet’
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
Here is one example how you may list all Kubernetes containers running in docker:
– ‘docker ps -a | grep kube | grep -v pause’
Once you have found the failing container, you can inspect its logs with:
– ‘docker logs CONTAINERID’
error execution phase wait-control-plane: couldn’t initialize a Kubernetes cluster