kubernetes-sigs / kubespray

Deploy a Production Ready Kubernetes Cluster
Apache License 2.0
16.2k stars 6.48k forks source link

Release proposal v2.25.1 #11621

Closed robertvolkmann closed 2 weeks ago

robertvolkmann commented 1 month ago

Changes by Kind

Deprecation / Removal

Feature

Applications

Network

Container-Managers

Bug or Regression

VannTen commented 1 month ago

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 commented 1 month ago

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

tico88612 commented 1 month ago

@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 commented 1 month ago

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

VannTen commented 1 month ago

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

tico88612 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

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

tico88612 commented 1 month ago

@robertvolkmann Please add #11638 to bugfix paragraph.

(Waiting for HTTP 429 error cooldown and retest.)

tico88612 commented 1 month ago

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

enneitex commented 4 weeks ago

Hey, can we add https://github.com/kubernetes-sigs/kubespray/pull/11666 to the release note ?

robertvolkmann commented 3 weeks ago

@enneitex done.

janosbabik commented 2 weeks ago

Hello beautiful people, do we have a release time for this new version? :)

VannTen commented 2 weeks ago

@yankay We can release as-is, I think.

yankay commented 2 weeks ago

Thanks @robertvolkmann @VannTen @tico88612 Greate Appreciate. It has been released :-)