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

[wait-control-plane] Waiting for the kubelet to boot up the control plane as sta                                  tic Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
Unfortunately, an error has occurred:
        timed out waiting for the condition
This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
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

Solutions

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

Fix

sudo swapoff -a
sudo sed -i '/ swap / s/^/#/' /etc/fstab
# Reboot a machine after that.
kubeadm reset
kubeadm init --ignore-preflight-errors all

«

Prev

1

/

1

Next

»

Kubernetes – CKA Certification Overview – By DevOpsSchool.com

Kubernetes – CKA Certification | Part 1 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 2 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 3 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 4 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 5 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 6 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 7 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 8 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 9 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 10 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 11 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 12 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 13 out 14 | — By DevOpsSchool

Kubernetes – CKA Certification | Part 14 out 14 | — By DevOpsSchool

«

Prev

1

/

1

Next

»

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand. 

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND