Controller does not start when upgrading to latest use-gocsi issue

[cristi-vlad]

vSphere Server Info

• vSphere version: Latest

Rancher Server Setup

• Rancher version: 2.7.5
• Installation option (Docker install/Helm Chart): Rancher helm charts through terraform
  • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1
• Proxy/Cert Details:

Information about the Cluster

• Kubernetes version: V1.23.16
• Cluster Type (Local/Downstream): Downstream
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported

Describe the bug
What happened:

When trying to upgrade vsphere csi driver in rancher rk1 from 2.5.1 to latest, vsphere-csi-controller container in vsphere-csi-controller pod is not starting, having following error:

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

To Reproduce

Clean install (or upgrade) of latest rancher helm chart of vsphere-csi and vsphere-cpi

Result

vsphere-csi-controller is not starting

Expected Result

vsphere-csi-controller is starting

Screenshots
N/A

Additional context
I think is related to this:

vsphere-charts/charts/rancher-vsphere-csi/templates/controller/deployment.yaml

Line 119 in 8b8e8cf

- "--use-gocsi=false"

Please check also: kubernetes-sigs/vsphere-csi-driver#2439 (comment)