Upgrading from kubespray 2.25.1 to 2.26.0 is a downgrade

[rptaylor]

What happened?

The v2.25.1 tag has:

• runc 1.1.14
• containerd 1.7.22
• etcd 3.5.16
• nerdctl 1.7.7

The v2.26.0 tag has (see checksums.yml)

• runc 1.1.13
• containerd 1.7.21
• etcd 3.5.12
• nerdctl 1.7.6

The release-2.26 branch has updates since the v2.26.0 tag:

• [2.26] Bump containerd 1.7.23 #11643 updates containerd to 1.7.23
• [2.26] Make Kubernetes v1.30.6 default #11673 updates k8s to 1.30.6
• a lot of other fixes that seem possibly important?

But even in the latest commits of the release-2.26 branch, nerdctl, etcd and runc remain lower versions than in 2.25.1

What did you expect to happen?

When upgrading Kubespray to a newer tagged release, all the components would be upgraded to newer versions.

How can we reproduce it (as minimally and precisely as possible)?

Look at the checksums.yml files I linked.

OS

RHEL 9

Version of Ansible

N/A

Version of Python

N/A

Version of Kubespray (commit)

f9ebd45

Network plugin used

calico

Full inventory with variables

N/A

Command used to invoke ansible

N/A

Output of ansible run

N/A

Anything else we need to know

No response

[rptaylor]

I made #12817 for this.

[rptaylor]

Now that #12817 is merged, any chance you could make a 2.26.1 tag @yankay ? :)