Bump sigs.k8s.io/cluster-api-provider-vsphere from 1.0.1 to 1.9.0

[dependabot[bot]]

Bumps sigs.k8s.io/cluster-api-provider-vsphere from 1.0.1 to 1.9.0.

Release notes

Sourced from sigs.k8s.io/cluster-api-provider-vsphere's releases.

v1.9.0

Highlights

• Based on Cluster API v1.6
• Support for Kubernetes v1.29
• Major overhaul of logging
• Improved e2e test coverage
• Reduced dependencies in main go.mod file by introducing a test/go.mod.

Changes since v1.8.0

:chart_with_upwards_trend: Overview

• 226 new commits merged
• 1 breaking change :warning:
• 13 feature additions ✨
• 14 bugs fixed 🐛

:warning: Breaking Changes

• Remove v1alpha3 and v1alpha4 apiVersions (#2414)
  • Similar to when we removed the apiVersions in core CAPI we fixed the reconciliation of apiVersions in ownerRefs in v1.8.2. Removal of a deprecated APIVersion in Kubernetes [can cause issues with garbage collection by the kube-controller-manager] (kubernetes/kubernetes#102641) This means that some objects which rely on garbage collection for cleanup, may not be cleaned up properly if those objects were created with an APIVersion which is no longer served. To avoid these issues it’s advised to ensure a restart to the kube-controller-manager is done after upgrading to CAPV v1.9. This can be accomplished with any Kubernetes control-plane rollout, including a Kubernetes version upgrade, or by manually stopping and restarting the kube-controller-manager.

:sparkles: New Features

• Add k8s v1.29.0 ova's (#2561)
• Adds new field to set the minimum hardware version (#2509)
• Bump Cluster API to v1.6.0-beta.1 (#2463)
• Improve logging & error handling (#2527)
• Prepare main branch for release-1.9 development (#2461)
• Refactor context for vsphereclusteridentity controller (#2374)
• Refactor context for vspheredeploymentzone controller (#2369)
• Refactor context for vspheremachine controller (#2376)
• Refactor context for vspherevm controller (#2398)
• Remove previously deprecated code (#2451)
• Set InternalDNS address for machines (#2529)
• Set up golang context when initiating controller manager (#2339)
• Update kustomization.yaml to support kustomize v5 (#2523)

:bug: Bug Fixes

• ClusterCacheTracker: Use RequeueAfter 1 minute instead of immediate requeue when ErrClusterLocked gets returned to not fall into exponential requeue (#2528)
• Fix nil pointer error in retrieveVcenterSession (#2303)
• Fix potential panics when retrieving VSphereCluster from Cluster.spec.infrastructureRef (#2505)
• Fix watch & log of ProviderServiceAccount controller (#2592)
• Flatcar: Run kubeadm after containerd (#2405)
• Force logout of sessions in case of errors (#2530)
• Handle missing VSphereFailureDomain on VSphereDeploymentZone deletion (#2351)
• Improve clustermodule existence check (#2535)
• Re-add return on vimmachine error (#2473)
• Remove the conditional on ipv6 (#2397)
• Skip updating VMOp immutable fields (#2566)
• StoragePolicy should select datastore based on connected hosts and set on VM spec (#2134)
• Test: use GinkgoRecover in go subroutine of ownerreference test (#2552)

... (truncated)

Commits

• ea2dd15 Merge pull request #2624 from chrischdi/pr-bump-cpi-1-29-0
• b9b2c22 Merge pull request #2621 from sbueringer/pr-fix-images
• f298829 Bump cloud-provider vsphere to v1.29.0
• 768b573 Merge pull request #2622 from sbueringer/pr-bump-CAPI
• 3233ffe Merge pull request #2620 from sbueringer/pr-clarify-capv-releases
• dcf7670 Bump CAPI to v1.6.1
• cf557b7 Fix images in troubleshooting doc
• aab90fa Clarify our goals for CAPV releases related to CAPI, CPI and Kubernetes
• 8e0c5c4 Merge pull request #2619 from sbueringer/pr-bump-apidiff
• 0bb7acc Bump go-apidiff to v0.8.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[eks-distro-bot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a aws 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.

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.

[eks-distro-bot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
eks-anywhere-presubmit	c0b12febea2cf0f046ee9bfb308222a38d026a71	link	true	/test eks-anywhere-presubmit
eks-anywhere-e2e-presubmit	c0b12febea2cf0f046ee9bfb308222a38d026a71	link	true	/test eks-anywhere-e2e-presubmit
eks-anywhere-cli-attribution-presubmit	c0b12febea2cf0f046ee9bfb308222a38d026a71	link	true	/test eks-anywhere-cli-attribution-presubmit
eks-anywhere-generate-files-presubmits	c0b12febea2cf0f046ee9bfb308222a38d026a71	link	true	/test eks-anywhere-generate-files-presubmits

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[dependabot[bot]]

Superseded by #7713.