Issue with vsphere-csi-controller-deployment.yaml

[mattrcampbell]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:

Deploying syncer with vsphere-csi-controller-deployment.yaml results in the following error:

"flag provided but not defined: -leader-election"

Using the image "gcr.io/cloud-provider-vsphere/csi/release/syncer:v1.0.2"

What you expected to happen:

Syncer would start normally.

How to reproduce it (as minimally and precisely as possible):

Kubectl apply -f vsphere-csi-controller-deployment.yaml

Anything else we need to know?:

Environment:

• csi-vsphere version: v1.0.2
• vsphere-cloud-controller-manager version: v1.1.0
• Kubernetes version: 1.17.4
• vSphere version: 6.7 u3
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[divyenpatel]

v1.0.2 does not have -leader-election support.

leader-election support is added in v2.0.0 as mentioned in the #151

If you are interested in trying out 2.0 driver, you can use following images generated for above pull request.

gcr.io/cloud-provider-vsphere/csi/ci/driver:v1.0.2-257-g51199e1
gcr.io/cloud-provider-vsphere/csi/ci/syncer:v1.0.2-257-g51199e1

Once 2.0 driver is released, we will update yamls.

[mattrcampbell]

That makes sense. The old YAML files listed in the instructions went away, so you can no longer follow the directions at: https://github.com/kubernetes/cloud-provider-vsphere/raw/master/manifests/controller-manager/vsphere-cloud-controller-manager-ds.yaml
s

I went looking for files and these were the ones I found.

[divyenpatel]

@mattrcampbell we will put back older yamls for v.1.0.2 driver with this PR - #179

cc: @SandeepPissay @manojvs157

[divyenpatel]

fixed with #179