Question

You deploy a new Deployment with 3 replicas, but all its Pods remain in the Pending state indefinitely. Existing Pods on the cluster continue running normally. Running 'kubectl get pods -o wide' shows the new Pods have no assigned node, and 'kubectl describe pod' shows no scheduling events at all (not even FailedScheduling). Node resources are plentiful and there are no taints. Which action is the most appropriate next step to diagnose the root cause?

Accepted Answer

Check the status and logs of the kube-scheduler static Pod in the kube-system namespace on the control-plane node

Answer

Delete and recreate the Deployment to force the scheduler to reassign the Pods

Answer

Add more worker nodes to the cluster to increase available scheduling capacity

Answer

Restart the kubelet service on all worker nodes to re-register them with the API server