What happened:
I have Kubernetes clusters operating on VMware Cloud, hosted on AWS. The cluster is equipped with vSphere CSI drivers as a default configuration. Currently, I'm working with an external NFS storage solution that's accessible from my cluster. Despite my attempts to leverage the vSphere CSI driver to establish a connection with PV with this NFS device, I'm encountering issues. The YAML snippet I utilized for creating the storage class is provided below.
What happened: I have Kubernetes clusters operating on VMware Cloud, hosted on AWS. The cluster is equipped with vSphere CSI drivers as a default configuration. Currently, I'm working with an external NFS storage solution that's accessible from my cluster. Despite my attempts to leverage the vSphere CSI driver to establish a connection with PV with this NFS device, I'm encountering issues. The YAML snippet I utilized for creating the storage class is provided below.
The PV is not bound and it is in pending state. The error I see in PVC is
waiting for a volume to be created, either by external provisioner "csi.vsphere.vmware.com" or manually created by system administrator
What you expected to happen:
I expect the PV to be bound and I should be able to create PVCs
How to reproduce it (as minimally and precisely as possible): Use the above storage class and try .
Anything else we need to know?:
Environment: