kubeadm init - api server failed to start

thecrusher

any ideas?

[control-plane-check] kube-controller-manager is healthy after 4.406646704s
[control-plane-check] kube-scheduler is healthy after 6.006977953s
[control-plane-check] kube-apiserver is not healthy after 4m0.001158586s

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.
Here is one example how you may list all running Kubernetes containers by using crictl:
- 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID'
error execution phase wait-control-plane: failed while waiting for the control plane to start: kube-apiserver check failed at https://10.244.3.212:6443/liv
ez: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
To see the stack trace of this error execute with --v=5 or higher

thecrusher

doh i didn't see the hosts entries we had to add. problem solved. user error.

thecrusher

nope same thing happened again even after the edit to hosts file

chrispokorni

Hi @thecrusher,

Are you seeing these errors on the hosted lab environment or your own infrastructure?
If your own infrastructure, then what type of infrastructure is hosting your VMs? Are there any firewalls blocking inbound traffic to your VMs? What are the sizes of the VMs (CPU, RAM, vDisk), how many private network interfaces, and what OS is running them? Ensure all inbound traffic is allowed from all sources, all protocols, to all destinations.
What are the entries in your hosts file? What are the IP addresses and hostnames of your VMs?

Regards,
-Chris