Pods are stuck in the Pending state

Once pods are created but not run yet, they remain in the Pending state before switching to the Running state. To start running on a node, pods wait for certain conditions to be met, and if they are not, the pods get stuck in the Pending state.

There might be several possible reasons for this behavior. Follow the instructions below one by one until the issue is resolved.

There are not enough resources on the node to run the pod

The node has reached its capacity for pods

The resource limit set by the ResourceQuota or LimitRange objects has been reached in the namespace

The pod has requirements and scheduling policies that none of the nodes can meet

The pod has issues with the PV or PVC

Pods have conflicts when using the hostPort setting

The pod cannot be scheduled because the Topology Spread Constraints policy is violated

The pod has a low priority while the pressure on resources is high

The pod has issues with access to Docker images

Errors in integration with the container network interface (CNI) or the container storage interface (CSI)

If the issue persists, contact technical support.

Was this article helpful?

Was this article helpful?