🌱 Prepare main branch for v1.12 development

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:
Tests for kubernetes-sigs#3159

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[sbueringer]

/test ?

[team-cluster-api-prow]

@sbueringer: The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-31-1-32-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-main
• /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
• /test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main
• /test pull-cluster-api-provider-vsphere-test-main
• /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-vsphere-apidiff-main
• /test pull-cluster-api-provider-vsphere-janitor-main

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-vsphere-apidiff-main
• pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
• pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
• pull-cluster-api-provider-vsphere-test-main
• pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test ?

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.

[sbueringer]

/test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-31-1-32-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
/test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
/test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main

[sbueringer]

/test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main
/test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-31-1-32-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
/test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
/test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main

[sbueringer]

Probably flake

/test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main

[sbueringer]

/close