Release proposal v2.25.1

[robertvolkmann]

Changes by Kind

Deprecation / Removal

• Deprecating support for Centos7 and Weave ; they are not tested anymore (#11428, @k8s-infra-cherrypick-robot)
• Remove Debian 10 support. (#11429, @k8s-infra-cherrypick-robot)ra-cherrypick-robot)

Feature

• Default to kubernetes v1.29.9 (#11599, @robertvolkmann)
• Add hashes for Kubernetes v1.29.7 (#11408, @mzaian), Add hashes for Kubernetes v1.29.6 (#11355, @tico88612)
• Default to etcd v3.5.16 (#11576, @janosbabik)
• [ingress-nginx] upgrade controller to version 1.11.2 (#11464, @k8s-infra-cherrypick-robot)
• Allow to run kubespray with an empty kube_node group, to provision only the control plane (#11249, @k8s-infra-cherrypick-robot)
• CentOS 7 yum repo baseurl update (#11365, @k8s-infra-cherrypick-robot)
• Check CentOS-Base.repo exists for CentOS 7 (#11438, @k8s-infra-cherrypick-robot)
• User has a possibility to fix nodePort of ingress-nginx service with property in addons.yaml (#11339, @k8s-infra-cherrypick-robot)

Applications

• [helm] Upgrade to v3.14.4 (#11599, @robertvolkmann)

Network

• [calico] Update default calico to v3.27.4 [calico] Fix high cpu load due to XDP program in iptables (#11476, @mzaian)

Container-Managers

• [containerd] Default to v1.7.22 [nerdctl] Upgrade to 1.7.7 [runc] Upgrade to v1.1.14 (#11576, @janosbabik)

Bug or Regression

• Always copy cert generation script to first etcd to pick up fixes on existing clusters (#11616, @k8s-infra-cherrypick-robot)
• Ingress-nginx-controller admission service is automatically created when ingress_nginx_webhook_enabled: true (#11332, @k8s-infra-cherrypick-robot)
• Fix: cannot stop & remove all cri containers via remove_node.yml (#11638, @k8s-infra-cherrypick-robot)

[VannTen]

We should probably come up with consistent guidance on what /kind to use for versions upgrades, because we're all over the place ^. Besides, look ok to me, and I don't have anything in mind which needs backporting.

@yankay

[tico88612]

Feature paragraph: Make kubernetes v1.29.7 default and Default Kubernetes version change to 1.29.6 I think you can simplify it.

[tico88612]

@VannTen We really need to organize our use of /kind, and I've been part of a Kubernetes release team that has clarified some of the ways it's used.

[robertvolkmann]

I reorganized the release notes to align to the previous releases.

[VannTen]

Is there a link/docs to that ? I'm all for aligning ourselves with the broader k8s community, especially on tooling.

[tico88612]

Is there a link/docs to that ? I'm all for aligning ourselves with the broader k8s community, especially on tooling.

I can't find the document now (but I think there should be guidelines); I'll edit it if I see it. https://github.com/kubernetes/kubernetes/labels?q=kind

The flaky label means some sporadic CI test failures have occurred. The failing-test label means CI test failures consistently or frequently. Refactor code I think is cleanup label. For the rest of the labels, I think we've used them pretty much the same way as before.

[yankay]

Thanks @robertvolkmann

It's awesome. 🎉 I think it's good enough to release. And if there are no block issue reported, I will release it in 3 days.

/lgtm

[yankay]

We should probably come up with consistent guidance on what /kind to use for versions upgrades, because we're all over the place ^. Besides, look ok to me, and I don't have anything in mind which needs backporting.

@yankay

Good Suggesstion.

The release note recently was autogenerated by https://github.com/kubernetes-sigs/kubespray/blob/master/RELEASE.md#release-note-creation and edited manually to make it more readable.

[tico88612]

@yankay #11627 is being fixed, and I'll send a PR to the release-2.25 branch later.

[tico88612]

@robertvolkmann Please add #11638 to bugfix paragraph.

(Waiting for HTTP 429 error cooldown and retest.)

[tico88612]

I think we don't have any blocker issue on release-2.25 branch, I think it is ready to release v2.25.1.