vSphere CSI Driver 3.0.2: "flag provided but not defined: -use-gocsi"

[hyorch]

Error using vSphere CSI Driver v3.0.2

Environment:

• Cloud provider or hardware configuration:
  vSphere 7.0u3

Kubespray version (commit) (git rev-parse --short HEAD):
v2.22.1 and v2.23.0

vSphere CSI Parámeters

# Vsphere version where located VMs
external_vsphere_version: "7.0u3"
vsphere_syncer_image_tag: "v3.0.2"
vsphere_csi_attacher_image_tag: "v4.2.0"
vsphere_csi_controller: "v3.0.2"
vsphere_csi_liveness_probe_image_tag: "v2.9.0"
vsphere_csi_provisioner_image_tag: "v3.4.0"
vsphere_csi_snapshotter_image_tag: "v6.2.1"
vsphere_csi_node_driver_registrar_image_tag: "v2.7.0"
vsphere_csi_driver_image_tag: "v2.5.1"
vsphere_csi_resizer_tag: "v1.7.0"
# To use vSphere CSI plugin to provision volumes set this value to true
vsphere_csi_enabled: true
vsphere_csi_controller_replicas: "2"

When deploying vSphere CSI Driver version 3.0.0, 3.01 and 3.0.2 you get this error on Pod: vsphere-csi-controller-xxx container: vshpere-csi-controller, and container exits.

 k -n kube-system logs -f vsphere-csi-controller-8645c49956-svwb2 --container vsphere-csi-controller
flag provided but not defined: -use-gocsi
Usage of /bin/vsphere-csi:
  -fss-name string
        Name of the feature state switch configmap
  -fss-namespace string
        Namespace of the feature state switch configmap
  -kubeconfig string
        Paths to a kubeconfig. Only required if out-of-cluster.
  -supervisor-fss-name string
        Name of the feature state switch configmap in supervisor cluster
  -supervisor-fss-namespace string
        Namespace of the feature state switch configmap in supervisor cluster
  -version
        Print driver version and exit

Kubespray template for CSI Pod, https://github.com/kubernetes-sigs/kubespray/blob/v2.23.0/roles/kubernetes-apps/csi_driver/vsphere/templates/vsphere-csi-controller-deployment.yml.j2, is still adding a parameter that is not allowed on CSI Driver 3.0.0 and not include in manual deployment templates https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/v3.0.2/manifests/vanilla/vsphere-csi-driver.yaml

Kubespray

 - name: vsphere-csi-controller
          image: {{ gcr_image_repo }}/cloud-provider-vsphere/csi/release/driver:{{ vsphere_csi_controller }}
          args:
            - "--fss-name=internal-feature-states.csi.vsphere.vmware.com"
            - "--fss-namespace={{ vsphere_csi_namespace }}"
            - "--supervisor-fss-namespace={{ vsphere_csi_namespace }}"
            - "--use-gocsi=false"

Manual

 - name: vsphere-csi-controller
          image: gcr.io/cloud-provider-vsphere/csi/release/driver:v3.0.2
          args:
            - "--fss-name=internal-feature-states.csi.vsphere.vmware.com"
            - "--fss-namespace=$(CSI_NAMESPACE)"

Removing extraparameters in Kubernetes vsphere-csi-controller Deployment after deploying Kubespray, fix the issue, so this 2 extra parameters should be removed when using CSI version 3.0.0 and laters.

[mzaian]

Hello @hyorch

I will have a look.

/assign @mzaian