yeah, upstream docs specifically tell you not to use nodeName with WaitForFirstConsumer.
creamy-pencil-82913
01/25/2024, 8:12 PM
you can change the binding mode, or use node selector instead of nodeName.
creamy-pencil-82913
01/25/2024, 8:13 PM
this is a limitation of the Kubernetes PV binding process, not anything in the provisioner.
b
broad-dream-81849
01/25/2024, 8:16 PM
Awesome, thanks for pointing this out, I missed it. I was trying to recreate an already existing Pod (with the Go client) just reusing the same configuration that I received from the Get. It took me a while to find out that the nodeName was causing the issue