You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you choose to use WaitForFirstConsumer, do not use nodeName in the Pod spec to specify node affinity. If nodeName is used in this case, the scheduler will be bypassed and PVC will remain in pending state.
Instead, you can use node selector for kubernetes.io/hostname
Creating a pod without the
nodeName
being specified hangs the provisioning of the PVC, because of theWaitForFirstConsumer
volume binding mode.Test
nodeName
where the Pod should be scheduled hangs 🔴PVC log:
Fixes
Two possible fixes:
volume.kubernetes.io/selected-node
annotationvolumeBindingMode
toImmediate
References
I think this is related, so not sure if this is an actual problem/bug, or not.
The text was updated successfully, but these errors were encountered: