Crashing vsphere-csi-controller with RWX (ReadWtiteMany) PV #2755
Comments
|
@dzanto Did you disable |
|
kind: ConfigMap
apiVersion: v1
metadata:
annotations:
meta.helm.sh/release-name: vsphere-csi
meta.helm.sh/release-namespace: kube-system
labels:
app.kubernetes.io/managed-by: Helm
name: internal-feature-states.csi.vsphere.vmware.com
namespace: kube-system
data:
async-query-volume: 'false'
block-volume-snapshot: 'false'
cnsmgr-suspend-create-volume: 'false'
csi-auth-check: 'false'
csi-migration: 'false'
csi-windows-support: 'false'
improved-csi-idempotency: 'false'
improved-volume-topology: 'false'
list-volumes: 'false'
max-pvscsi-targets-per-vm: 'false'
online-volume-extend: 'false'
pv-to-backingdiskobjectid-mapping: 'false'
topology-preferential-datastores: 'false'
trigger-csi-fullsync: 'false'
use-csinode-id: 'true'I create custom StorageClass with apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: vsphere-nfs
parameters:
csi.storage.k8s.io/fstype: nfs4
provisioner: csi.vsphere.vmware.com
reclaimPolicy: Delete
volumeBindingMode: ImmediateBut when I create PVC, PV doesn't appear. apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-client-pvc
spec:
storageClassName: vsphere-nfs
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10MiRWX work only when I create PVC and PV manually, how there https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-static-fileshare-provisioning.yaml How automatically create PV? |
|
Looks like the vSphere CSI driver was not deployed properly. vSphere CSI driver v3.0.1 has |
|
I use rancher's helm chart: https://artifacthub.io/packages/helm/rke2-charts/rancher-vsphere-csi In this |
|
The topology flag in provisioner is set to false by default in our YAML as well. It is only set to true when a customer chooses to use topology in their environment. The |
|
I added |
|
Can you post the logs when you set |
|
|
Hi, have you found a solution ? I have the same issue with my clusters rke2 and k3s and the helm charts rancher-vsphere-csi:103.0.0+up3.0.2-rancher1 Anything else we need to know?: The vSAN File Service is working because I tried to create a File NFS share and I able to mount it manually on a node of the k8s cluster Environment:
|
|
Ok after few weeks I found the solution Edit in your configMap :
Restart Pods of the vSphere plugin and recreate PVC @dzanto Let me know if this helped you |
/kind bug
What happened:
I have install vSphere Cloud Provider Interface (CPI) and vSphere Container Storage Interface (CSI) to kubernetes cluster from Rancher Apps, and mount RWO (ReadWtiteOnce), it's works fine.
Then I try to create PVC (PersistentVolumeClaim) with RWX (ReadWtiteMany) mode, but csi-provisioner and vsphere-csi-controller begin restarting with logs:
csi-provisioner:
vsphere-csi-controller
Environment:
The text was updated successfully, but these errors were encountered: