Create a dedicated vSphere CCM secret

[xmudrii]

What this PR does / why we need it:

Currently, we're creating a single secret to be used for both machine-controller and vSphere CCM. The vSphere CCM requires that the secret data is in the format of <vcenter-address>.username and <vcenter-address>.password, while the machine-controller requires the secret data in the format of VSPHERE_*.

The problem is that the vSphere CCM fails to parse the secret if there are any other fields than <vcenter-address>.username and <vcenter-address>.password. That causes authorization failures, so node metadata would not be populated from the API, as well as, it would not be possible to use volumes.

To fix this issue, this PR introduces another secret, that would be used only for the vSphere CCM. The secret is called vsphere-ccm-credentials and is located in the kube-system namespace.

Both in-tree CCM and the external CCM are affected.

Reference: https://github.com/kubernetes/kubernetes/blob/e0aeb1b17d6bfc180de62c1adce39b38238176fc/staging/src/k8s.io/legacy-cloud-providers/vsphere/credentialmanager.go#L137-L169

Does this PR introduce a user-facing change?:

Create a dedicated vSphere CCM secret to be used by kube-controller-manager/external CCM

/assign @kron4eg

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [xmudrii]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubermatic-bot]

LGTM label has been added.

Git tree hash: d0f1952a8cc74243a92fbbbde7575870ac48a7fd

[kron4eg]

/cherrypick release/v1.0

[kubermatic-bot]

@kron4eg: once the present PR merges, I will cherry-pick it on top of release/v1.0 in a new PR and assign it to you.

In response to this:

/cherrypick release/v1.0

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.

[kubermatic-bot]

@kron4eg: new pull request created: #1129

In response to this:

/cherrypick release/v1.0

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.