Question

After a maintenance reboot of a single-node control plane, `kubectl get nodes` fails with 'The connection to the server 10.0.0.5:6443 was refused'. You SSH into the control-plane node. `systemctl status kubelet` shows kubelet is active and running. You need to find out why the kube-apiserver static pod is not serving requests. What is the BEST first step to diagnose the failure?

Accepted Answer

Inspect container runtime logs directly with `crictl ps -a` and `crictl logs <apiserver-container-id>` on the node

Answer

Run `kubectl logs -n kube-system kube-apiserver-<node>` to view the API server logs

Answer

Restart the kubelet with `systemctl restart kubelet` and wait for the API server to recover

Answer

Edit `/etc/kubernetes/manifests/kube-apiserver.yaml` to add a readiness probe and let kubelet recreate the pod