Question

You SSH into a control-plane node after users report that all kubectl commands fail with 'The connection to the server 10.0.1.5:6443 was refused - did you specify the right host or port?'. The node itself is up and other cluster nodes are Ready according to a monitoring dashboard cached minutes ago. The API server runs as a static pod managed by kubelet. Which command sequence will most directly help you diagnose why the API server is not responding?

Accepted Answer

Run 'sudo crictl ps -a' to check the kube-apiserver container state, then 'sudo crictl logs <container-id>' to inspect its output

Answer

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

Answer

Run 'kubectl describe pod -n kube-system kube-apiserver-<node>' to see recent events

Answer

Run 'systemctl restart kubelet' immediately to force the API server to restart