An MLOps engineer is deploying a training pod that requires a high-performance volume. After applying the pod and PVC manifests, the pod remains in a 'Pending' state. The engineer runs
'kubectl describe pod training-pod-7d8c' and sees the following event:
Events:
Type Reason Age From Message
- - - -
Warning FailedScheduling 2m15s
default-scheduler 0/4 nodes are available: 1 node(s) had volume node affinity conflict, 3 node(s) didn't find available persistent volume to bind.
The engineer then inspects the associated PVC and sees its status is also 'Pending'.
What is the most likely cause of this issue?