CSI Driver 3.2 in Single VC data center fails to provision

[rajasec]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug /kind feature

What happened: We have the following setup in our Data center with following setup. DC1 Zone1 Host 1 DataStore 1 Host 2 DataStore 2 Zone 2 Host 1 DS3 Host2 DS4 Host 3 DS5

There isy no shared datastore across the clusters. No VSAN too. When we try to create the volume in Zone1/Host1/DS1 using datastore url, it is throwing out the error as No compatible datastores found for accessibility requirements [map......] pertaining to vCenter x.x.x.x

Not sure with 3.1.0 onwards shared datastore is mandatory need within cluster to create volume.

What you expected to happen: Volume to bound after applying How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?: @shalini-b, is there any hard requirement to have shared data stores from 3.1 onwards, as datastore url is not having effect inside the code, because it is trying to check whether DS is accessible from other host also. Environment:

• csi-vsphere version: 3.2
• vsphere-cloud-controller-manager version:
• Kubernetes version: 1.29.6
• vSphere version:
• OS (e.g. from /etc/os-release): Ubuntu 22.
• Kernel (e.g. uname -a): 5.15
• Install tools:
• Others:

[rajasec]

@divyenpatel @shalini-b For 3.2 version whether shared datastore or vSAN is mandatory. As we dont have vSAN and shared datastore, we are not able to provision the volume becuse of No compatible datastores found error.