Can i create ReadWriteMany pvc on VVOL datastore?

[dhlfs]

This form question about feature:

/kind feature

What happened:
Trying to create pvc with ReadWriteMany option enabled and get error:

kubectl describe pvc
Name:          vvol-test-many02
Namespace:     default
StorageClass:  k8s-vvol-datastore-test
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: csi.vsphere.vmware.com
               volume.kubernetes.io/storage-provisioner: csi.vsphere.vmware.com
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type     Reason                Age                From                                                                                                 Message
  ----     ------                ----               ----                                                                                                 -------
  Normal   ExternalProvisioning  10s (x2 over 18s)  persistentvolume-controller                                                                          waiting for a volume to be created, either by external provisioner "csi.vsphere.vmware.com" or manually created by system administrator
  Normal   Provisioning          3s (x5 over 18s)   csi.vsphere.vmware.com_vsphere-csi-controller-7ff8bd68bb-fcv6d_767bd14b-2cc2-4e81-ac6d-a5e3e5b55b75  External provisioner is provisioning volume for claim "default/vvol-test-many02"
  Warning  ProvisioningFailed    3s (x5 over 18s)   csi.vsphere.vmware.com_vsphere-csi-controller-7ff8bd68bb-fcv6d_767bd14b-2cc2-4e81-ac6d-a5e3e5b55b75  failed to provision volume with StorageClass "k8s-vvol-datastore-test": rpc error: code = Internal desc = no datastores found to create file volume

What you expected to happen:
Trying to create pvc with ReadWriteMany option

Anything else we need to know?:

Environment:

• csi-vsphere version: gcr.io/cloud-provider-vsphere/csi/release/driver:v2.4.1
• vsphere-cloud-controller-manager version:
• Kubernetes version: Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.2", GitCommit:"9d142434e3af351a628bffee3939e64c681afa4d", GitTreeState:"clean", BuildDate:"2022-01-19T17:29:16Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
• vSphere version: vCenter Version: 7.0.3, VMware ESXi, 7.0.2(17867351),
• OS (e.g. from /etc/os-release): Oracle Linux Server release 8.5
• Kernel (e.g. uname -a): 5.4.17-2136.302.7.2.el8uek.x86_64 Migrate CSI from k/cloud-provider-vsphere #2 SMP Wed Jan 5 19:12:52 PST 2022 x86_64 x86_64 x86_64 GNU/Linux
• Install tools: vmware tools 11.2.5.26209 (build-17337674)

[divyenpatel]

you can not.
we support creating RWM volume on the vSAN datastore only with vSAN file service enabled on the datastore.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[divyenpatel]

/remove-lifecycle rotten