📖 update supported Kubernetes versions

[sbueringer]

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
Update supported versions in the book to include 1.24.
I refactored the table a bit to improve readability + to be able to include v1.24 without adding another two columns.

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

[sbueringer]

/hold
until #6513 is merged

/cherry-pick release-1.1

[k8s-infra-cherrypick-robot]

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

In response to this:

/hold
until #6513 is merged

/cherry-pick release-1.1

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.

[killianmuldoon]

/retitle 📖 update supported Kubernetes versions
/lgtm

Aside - not a blocker - are we planning to drop 0.3/0.4/1.0 from the main version of the book ahead of the next release?

[sbueringer]

I'll use this PR to test some jobs (in addition to testgrid as the update test there run only once per day):

/test pull-cluster-api-e2e-workload-upgrade-1-24-latest-main
/test pull-cluster-api-e2e-full-main

[k8s-ci-robot]

@sbueringer: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-e2e-workload-upgrade-1-24-latest-main	d626b5c	link	false	/test pull-cluster-api-e2e-workload-upgrade-1-24-latest-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[sbueringer]

Aside - not a blocker - are we planning to drop 0.3/0.4/1.0 from the main version of the book ahead of the next release?

I don't know. On one side those versions are all out of support. On the other side we only kept the version page of the current book up-to-date. This means that we might lose the information which Kubernetes version we support in which CAPI version if we just drop it here (not sure, but we can verify the old books).

[sbueringer]

/hold cancel
/assign @fabriziopandini
Test failure is obviously unrelated and will be fixed elsewhere.

[chrischdi]

/lgtm

[sbueringer]

Added notes about labels/taints and criSocket

[enxebre]

@sbueringer are we currently running tests for kube >= 1.18?

[sbueringer]

@sbueringer are we currently running tests for kube >= 1.18?

We have one test where we install v1.18, then upgrade to v1.19 and then run conformance tests.

Most versions that we claim we have support for are only tested by upgrade tests. (https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api).

We only run more tests for v1.19 (min) and v1.24 (max) management clusters (e.g. capi-e2e-main uses v1.24, capi-e2e-mink8s-main uses v1.19). Those tests are using v1.24 as workload cluster version (and v1.23=>v1.24 for the upgrade).

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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

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

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6592

In response to this:

/hold
until #6513 is merged

/cherry-pick release-1.1

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.