Provide option to use `hostPath` as a source for `vsphere.conf` for helm

[Danil-Grigorev]

What would you like to be added?

Currently the source for vsphere.conf is ConfigMap/Secret but it is sometimes more convenient to store the content in the filesystem of the node. The pod can mount this path with hostPath option, but it needs to be configurable in the helm chart options.

Why is this needed?

This configuration option will streamline bootstrapping process for the component, when creation of ConfigMap or Secret can’t be automated, but the filesystem access is present, so a file can be created on the node first.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[zhanggbj]

/remove-lifecycle rotten