volumeBindingMode: WaitForFirstConsumer and FailedScheduling

I am using AWS EKS on several deployments and it seems they decided to change the volumeBindingMode to WaitForFirstConsumer recently. In theory this prevents the creation of volumes into availability zones that don’t have node available.

It has, however has introduced a bug that the volumes are not being provisioned anymore. I’m getting 3m25s Warning FailedScheduling pod/jupyter-chicocvenancio 0/2 nodes are available: 2 node(s) didn't find available persistent volumes to bind. from the pod.

119s Normal WaitForFirstConsumer persistentvolumeclaim/claim-chicocvenancio waiting for first consumer to be created before binding from the pvc.

I’m writing this to see if anyone is running into this as well, or maybe has some pointers in how to fix this properly.
For the moment I am using a new storageClass that has ´volumeBindingModeasImmediate`.

https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/1413 Seems very similar