kubernetes-retired/external-storage

[efs-provisioner] pvc not requested

keeganwitt opened this issue · 3 comments

We recently spun up a new EKS cluster, one of the pods successfully got pvc and pv sucessfully created through the provisioner, but two others (in the same namespace, and basically the same sets of YAMLs, it's just a different environment, so basically just different names) never got the pvc created, and I don't see any requests for those claims logged in the provisioner pod. What can I do to diagnose this further?

We are using Helm chart 0.6.0, which is Docker image quay.io/external_storage/efs-provisioner:v2.2.0-k8s1.12, which is release v2.2.0-k8s1.12 of this repo. The cluster is eks.8 (K8s 1.14).

I might be misunderstanding how this all works, but I assumed the provisioner started its work when a K8s event for the pvc occurs, but I didn't see any such event. The pod using the claim just says that it wasn't scheduled because the persistentvolumeclaim was not found.

I'm now thinking this is because of an order of operations issue with our setup. No storage type annotation was on the pvc, and maybe the default storage class changed during our setup (it is now a class that uses the kubernetes.io/aws-ebs provisioner).

Edit: actually, this was an issue with the order our TerraForm scripts were applied, so the PVC didn't get created before the pods that attempted to use it.