Question

A pod using a PersistentVolumeClaim backed by a local PersistentVolume is stuck in Pending. The PVC is Bound, and cluster nodes have ample CPU and memory. Running 'kubectl describe pod' shows the event: '0/4 nodes are available: 4 node(s) had volume node affinity conflict.' What is the most likely cause?

Accepted Answer

The PersistentVolume defines nodeAffinity restricting it to a node whose labels do not match any schedulable node, so the scheduler cannot place the pod.

Answer

The StorageClass has volumeBindingMode set to Immediate, which forces the pod onto a random node.

Answer

The PVC requests more storage than the PersistentVolume provides, preventing scheduling.

Answer

The pod is missing a nodeSelector, so the scheduler defaults to rejecting all nodes.