Question

You create a Deployment named 'web' with replicas set to 3, but after several minutes 'kubectl get pods' shows no pods at all for that Deployment. 'kubectl get deployment web' shows DESIRED 3 but CURRENT and AVAILABLE both 0, and no ReplicaSet exists. The scheduler and kubelets are healthy, and other existing pods run fine. Which action is the most appropriate first step to diagnose the root cause?

Accepted Answer

Inspect the kube-controller-manager static pod status and logs on the control-plane node (e.g., crictl/kubectl logs or /var/log/pods and the manifest in /etc/kubernetes/manifests)

Answer

Restart kube-scheduler because it is failing to bind the pods to nodes

Answer

Increase the Deployment's replica count to force the API server to create the ReplicaSet

Answer

Delete and recreate the CoreDNS pods to restore controller reconciliation