🌱 test: add coverage to find issues running on the next kubernetes release as management cluster

[chrischdi]

…ase as management cluster

What this PR does / why we need it:

This helps to find upcoming issues like the one fixed in:

• 🐛 Drop caBundle from CRDs to support Kubernetes 1.31 #10972

way more earlier in the cycle and not when we start bumping to beta or rc's for the management cluster.

/area e2e-testing

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 #

[chrischdi]

/test help

[k8s-ci-robot]

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cluster-api-build-main
• /test pull-cluster-api-e2e-blocking-main
• /test pull-cluster-api-e2e-conformance-ci-latest-main
• /test pull-cluster-api-e2e-conformance-main
• /test pull-cluster-api-e2e-main
• /test pull-cluster-api-e2e-mink8s-main
• /test pull-cluster-api-e2e-upgrade-1-30-1-31-main
• /test pull-cluster-api-test-main
• /test pull-cluster-api-test-mink8s-main
• /test pull-cluster-api-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-apidiff-main

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

• pull-cluster-api-apidiff-main
• pull-cluster-api-build-main
• pull-cluster-api-e2e-blocking-main
• pull-cluster-api-test-main
• pull-cluster-api-verify-main

In response to this:

/test help

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.

[chrischdi]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main
/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main
/test pull-cluster-api-e2e-upgrade-1-30-1-31-main

[chrischdi]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main
/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main
/test pull-cluster-api-e2e-upgrade-1-30-1-31-main

[chrischdi]

/retitle 🌱 [wip] test: add coverage to find issues running on the next kubernetes release as management cluster

We have to build the kind image.

[chrischdi]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main
/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main
/test pull-cluster-api-e2e-upgrade-1-30-1-31-main

[chrischdi]

/hold

For discussion on #10984 (comment)

[sbueringer]

/lgtm
/approve

Feel free to merge

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 205147fc07255845f805a92f57052b15513d913e

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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 [sbueringer]

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

[sbueringer]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.8

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.

[chrischdi]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main
/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main
/test pull-cluster-api-e2e-upgrade-1-30-1-31-main

/hold cancel

[sbueringer]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 9a3078ebbbac824d8e76564f75160c592e8c07ba

[fabriziopandini]

/lgtm

[sbueringer]

/hold

Maybe we're now really hitting the 2h timeouts regularly :)

Let's get more data and then talk about in on Monday (maybe we should increase the timeout & interval to 3h)

[sbueringer]

/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main

[sbueringer]

We've hit the timeout again

/test pull-cluster-api-e2e-main
/test pull-cluster-api-e2e-mink8s-main

[sbueringer]

Talked to Christian, we're going to increase the timeouts & intervals to 3h

[chrischdi]

xref: kubernetes/test-infra#33220

[sbueringer]

Merged

/hold cancel

/override pull-cluster-api-e2e-mink8s-main
(just a timeout, also worked before)
EDIT: ups, looks like the mink8s didn't work earlier

[k8s-ci-robot]

@sbueringer: Overrode contexts on behalf of sbueringer: pull-cluster-api-e2e-mink8s-main

In response to this:

Merged

/hold cancel

/override pull-cluster-api-e2e-mink8s-main
(just a timeout, also worked before)

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-e2e-mink8s-main

[sbueringer]

/hold

[sbueringer]

/hold cancel
(the job should now block merge)

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #11014

In response to this:

/cherry-pick release-1.8

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.