Comment by Saurabh Malpani on "How to Install a Kubernetes Cluster with Kubeadm, Containerd, and Cilium: A Hands-On Guide"

I have been trying to follow the steps here to play with Kubernetes for the very first time. The problem is that after the kubeadm is up and running on the master - after sometime the api server shuts down. Is there some recommendation on what may be going wrong or how to debug?

Thanks for trying this out. Can you share more details on the error you get when apiserver shuts down.

Santoshdts

So what happens for me is that after a while running kubctl get nodes returns:

kubectl get nodes The connection to the server 192.168.64.41:6443 was refused - did you specify the right host or port?

The api server doesn't show in the ps output.

I think after some time kubelet restarts the api server I get this :

kubectl get nodes Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get nodes)

And when I look around, the /var/log/controller and look at the api server response, I get very random log with errors that are not correlated.

Saurabh Malpani Sorry for the delay in responding. This issue initially looks due to some misconfig with the api-advertise-address,. Did you specify the correct API server address while kubeadm init ? You can also check the kubelet logs journalctl -fu kubelet, or check the pod logs at /var/log/pods/kube_system***/*** for APIserver pod.

Hope this would give a headstart.

Search Hashnode