🌱 Use latest kind images for CAPD

[sbueringer]

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

What this PR does / why we need it:

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 #7620

[sbueringer]

/assign @killianmuldoon
/assign @fabriziopandini

/cherry-pick release-1.3

[k8s-infra-cherrypick-robot]

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

In response to this:

/assign @killianmuldoon
/assign @fabriziopandini

/cherry-pick release-1.3

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.

[sbueringer]

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

[killianmuldoon]

/lgtm

[fabriziopandini]

Thanks for this change!
What about tracking this somehow on our release task list, so we periodically check we are running recent images?
cc @sbueringer @ykakarap
/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: #7644

In response to this:

/assign @killianmuldoon
/assign @fabriziopandini

/cherry-pick release-1.3

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.

[sbueringer]

@fabriziopandini I have "Ensure the latest available kind version is used as well." as part of our Kubernetes bump tracking issue: https://github.com/kubernetes-sigs/cluster-api/blob/main/.github/ISSUE_TEMPLATE/kubernetes_bump.md

I can add: ensure the latest kind images are used as a hint there as well.

I think I wouldn't add it on both lists as it's usually important in the context of the Kubernetes bump.

Context:

Usually it's like this: new Kubernetes release => new kind release (as part of that: new kind images)