Question

A newly deployed pod remains in the Pending state. Running 'kubectl describe pod web-7f9' shows the following event: 'Warning FailedScheduling ... 0/4 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 3 Insufficient cpu.' All three worker nodes are Ready. What is the most likely cause that must be addressed to schedule this pod?

Accepted Answer

The pod's CPU requests exceed the allocatable CPU remaining on every worker node, so no worker can satisfy the request.

Answer

The kube-scheduler is not running, preventing any pods from being scheduled.

Answer

The pod lacks a toleration for the control-plane taint, which is required to run on worker nodes.

Answer

CoreDNS is unavailable, so the scheduler cannot resolve the node names.