vSphere updates

[luringens]

/kind feature

What this PR does / why we need it:

Update vSphere CSI and CPI components, documentation and manifests, as the current defaults versions do not support the current default Kubernetes version.

Which issue(s) this PR fixes:

None.

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

- Action required
  The default versions for all vSphere components have been updated. The minimum supported vSphere version is now 7.0u1. Some of the new default versions of these components have a minimum supported Kubernetes version of 1.34; if you are not updating to Kubernetes 1.34 at the same time, you **must** pin these to a previous version. See [docs/CSI/vsphere-csi.md] for a list of variables to set.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: luringens / name: Viv (1313b1c, 3f0000c, 6368af8, 661325a, 6979cff, 81cec52, 9146dba)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: luringens
Once this PR has been reviewed and has the lgtm label, please assign tico88612 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @luringens. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[luringens]

Relates to #12406 in that it updates the manifests, but does not add support for multiple vcenters and zoning.

Marking as WIP as I haven't had a chance to test this yet, but I figured I'd put up the draft anyways.

[luringens]

Snapshotter v7 also notes that it needs to be reinstalled completely, so I need to look into how best to do that, or perhaps if it'll just have to be an action required changelog item.

https://github.com/kubernetes-csi/external-snapshotter/releases/tag/v7.0.0

edit: probably not relevant to a sidecar deployment

[yankay]

/ok-to-test

[luringens]

Deployed to our clusters and works well! 🙂

[tico88612]

/label tide/merge-method-merge

[tico88612]

I don't recommend continuing to maintain the yaml config (in Kubespray, this is out of scope for us). Is it possible to implement it using a helm chart instead?

[luringens]

It is probably possible, but I am no longer on our Kubernetes team and can't allocate more time to the project.

I hope this at least helps keep the config already present in a good state and supporting recent Kubernetes releases, even if it should be replaced in the future.

[tico88612]

It is probably possible, but I am no longer on our Kubernetes team and can't allocate more time to the project.

Oh, that's too bad. :(

I hope this at least helps keep the config already present in a good state and supporting recent Kubernetes releases, even if it should be replaced in the future.

It mainly comes down to whether the maintainers have the capacity to handle it; if we use Helm Charts, we don't have to worry about anything beyond the app itself.