Kubernetes 1.24 Release Timeline

[damemi]

From https://github.com/kubernetes/sig-release/blob/master/releases/release-1.24/README.md

The 1.24 release cycle is as follows:

• Monday 10th January 2022: Week 1 — Release cycle begins
• Thursday 27th January 2022: Week 3 — Production Readiness Soft Freeze
• 02:00 UTC Friday 4th February 2022: Week 4 — Enhancements Freeze
• Wednesday 23rd March 2022: Week 11 — [Release Retrospective][Retrospective Document] part 1
• 01:00 UTC Wednesday 30th March 2022: Week 12 — Code Freeze
• Tuesday 19th April 2022: Week 15 — Kubernetes v1.24.0 released

We will try to release the v0.24 Descheduler soon after Kubernetes 1.24 is released

---

Steps for Descheduler release:

• Bump k8s.io dependencies to rc post code freeze/prior to 1.24 release
  • (ex Bump to k8s 1.21-rc.0 #539) (nice to have)
• Bump k8s.io dependencies to GA 1.24 post release @JaneLiuL
  • (ex Bump To k8s 1.22.0 #615)
• Add release-1.24 branch tests and update old branch tests in k8s.io/test-infra @pravarag (Add descheduler 1.24 tests kubernetes/test-infra#25833)
• Update version references in docs/readme/compatibility matrix @pravarag
  • (ex Update Docs and Manifests for v0.22.0 #617)
• * Tag v0.24 from master @damemi
• * Update Helm chart @JaneLiuL
  • (ex Update helm chart version to v0.23 #709)
• * Cut release-1.24 branch @damemi
• Promote image from tagged branch commit
  • (ex Promote descheduler images to v0.23.0 kubernetes/k8s.io#3344)
• Publish release @damemi

• Note that to try addressing Currently, v0.23.0 image has wrong app version #736, we will create the v0.24 Git tag before cutting the release branch. But, in order for the automated Helm chart release action to work, it must detect some changes since the most recent tag. So, we will update the Helm chart after creating the tag but before creating the release-* branch, which is what triggers the automated Helm release action (see https://github.com/kubernetes-sigs/descheduler/blob/master/docs/release-guide.md#notes). Doing this will give us a v0.24-tagged SHA to promote from staging to the public image.

[JaneLiuL]

great to hear this good news! so may i ask that do i need to close the #737?

[JaneLiuL]

can i have a try on update descheduler for k8s 1.24?

[pravarag]

@damemi I would also like to take part in 1.24 release upgrades for descheduler, be it via or documentation or bumping the file versions. Kindly let me know :)

[JaneLiuL]

/assign

[damemi]

@JaneLiuL I think you can close #737
I'll make a list of the tasks that need to be done, and folks can feel free to create and self-assign new issues for each one 🙂 it will be great to have some more hands working on the release, and there is a lot of steps involved!

[damemi]

Updated the original comment with a list of tasks, anyone please let me know if I missed anything. Otherwise, feel free to self-assign any particular tasks you're interested in.

[pravarag]

Updated the original comment with a list of tasks, anyone please let me know if I missed anything. Otherwise, feel free to self-assign any particular tasks you're interested in.

Thanks for sharing the list of associated tasks. Wanted to check if the tasks are listed in the order of priority or all can be attempted once the code freeze happens for 1.24 release?

Also, I'd like to work on below two tasks if that's okay :) ,

[ ] Add release-1.24 branch tests and update old branch tests in k8s.io/test-infra
[ ] Update version references in docs/readme/compatibility matrix

@damemi

[damemi]

@pravarag updated with you on those tasks. I put the tasks in the general order that they should be done in. It's not too strict of an ordering (except for the tag/helm/branch part which is important to do in that order), so for most of them we can start whenever

[JaneLiuL]

@damemi may i take below tasks ?

*  Bump k8s.io dependencies to rc post code freeze/prior to 1.24 release
* Update Helm chart

[damemi]

@JaneLiuL yup, added you to the main description

[pravarag]

@damemi for adding 1.24 release branch tests we'll be removing 1.21 tests right and adding 1.24 tests? Like, does it support only upto 3 versions of K8s?

[damemi]

@pravarag yep, for the master and release-1.24 branches we don't need the 1.21 tests, we only test the three latest minor versions https://github.com/kubernetes-sigs/descheduler#compatibility-matrix

[pravarag]

@damemi wnated to check, we'll be merging changes for Descheduler w.r.t K8s release 1.24, post 19th of April or I can start making changes now as well?

[damemi]

@pravarag you can start opening PRs with the changes now. Some things like the test-infra changes may have to hold until we bump to 1.24, but it definitely doesn't hurt to get the PRs open early at least.

[damemi]

Just to bump this, the k8s 1.24 rc.0 release is planned for this Monday April 11! @pravarag has already opened the PR to add our 1.24 tests (kubernetes/test-infra#25833)

@JaneLiuL you volunteered to do the final GA bump, but just checking were you interested in doing an rc bump too once those tags are published next week?

[JaneLiuL]

hi @damemi thanks for notification~~ sure~ i will doing an rc bump too :). my honer to do that :)

[JaneLiuL]

still not discover the k8s 1.24 rc.0 release tag, i will keep eye on it :)

[damemi]

@JaneLiuL yeah the 1.24 release has hit some delays, see https://groups.google.com/a/kubernetes.io/g/dev/c/D0fGHU-9hKI

Also recommend subscribing to that group if anyone isn't already :)

[damemi]

Another update -- the 1.24 release is now delayed to May 3: https://groups.google.com/a/kubernetes.io/g/dev/c/9IZaUGVMnmo

[JaneLiuL]

Kubernetes v1.24.0-rc.0 has been release, but client-go or apiserver still don't release v1.24.0-rc.0 yet. i will waiting the client-go and apiserver release v1.24.0-rc.0 :)

[damemi]

@JaneLiuL thanks for the update! With the delays this release has been experiencing it's not totally surprising that there's hiccups with the client libraries too. No worries

[JaneLiuL]

:) open pr here for rc-0: #787

[jklaw90]

will this pr make it in to 1.24 #636?

[damemi]

will this pr make it in to 1.24 #636?

it will be tough, since that PR needs a rebase and there are still outstanding comments left on it. If @ingvagabund or @RyanDevlin are available to commit to addressing the last few nits then we can hold off the release for that PR

[jklaw90]

@damemi this issue is a very common in our clusters and we've been delaying increasing adoption of descheduler in our clusters because of it. My concern is certain workloads like workers or slower booting services can really be impacted by this. If you need help i could probably take a look too.

[ingvagabund]

Checking #636 now

[JaneLiuL]

bump k8s to 1.24.0 pr here: #791

[pravarag]

Added the following docs PR as well: #792

[JaneLiuL]

Update Helm chart pr: #796

[damemi]

At this point I'd like to cut the v0.24.0 git tag to start the final release process. Please let me know if there are any other changes that need to be merged into this release before that. Quickly reviewing the PRs that are open right now didn't show anything critical.

[damemi]

Tag created, and the images appear to be tagged with the right version now. Image promotion PR at kubernetes/k8s.io#3739

[damemi]

/close

[k8s-ci-robot]

@damemi: Closing this issue.

In response to this:

/close

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.