Hello Kubernetes community!
The 1.25 release cycle has begun and we are collecting enhancement information.
The Short Version
SIG leads must opt-in enhancements for Kubernetes 1.25 by entering KEP information into the enhancements tracking sheet[1].
There is one notable change from 1.24!
The KEP Template[3] has officially been updated to incorporate more detail in the Test Plan section[4] in furtherance of the goal of increasing reliability[5] across the project. Please be sure to include this updated Test Plan section in your PRs[6] as you begin to open and work on them for inclusion in 1.25.
This was communicated to d...@kubernetes.io, le...@kubernetes.io on May 11th, 2022[7].
Important Notes:
Enhancements freeze starts at 18:00 PST on Thursday, June 16th, 2022
When entering your enhancements into the spreadsheet, please indicate if docs are required in the "Needs Docs?" column.
Actions Required:
If you are a SIG Lead, discuss in your SIG which enhancements you will be proposing for the release, and enter them into the tracking spreadsheet.
If you are an enhancement author, remind your SIG that they must opt-in your enhancement. Your KEP must be merged and complete by the start of Enhancements Freeze.
Please join the #release-enhancements[8] channel on Slack to discuss enhancements for this release.
The Long Version
All enhancements that are intended for inclusion in Kubernetes 1.25 must be tracked by the Release Team. Kubernetes SIGs that wish to include enhancements must "opt-in" by entering details on the enhancements tracking sheet[1].
SIG leads should add information to the "KEP Collection" tab, entering:
The GitHub Issue number from k/enhancements[9]
The enhancement's name
The enhancement's assignee
The owning SIG
If docs will be required or not
A link to the KEP (if merged) or KEP pull request (if unmerged)
All enhancements must have a KEP[10] merged and meet the review requirements[11] before Enhancements Freeze starts at 18:00 PST on Thursday, June 16th, 2022. Enhancements missing this deadline will be removed from the release, unless an exception is filed, during the following day.
Enhancement authors should ensure that their enhancements meet the requirements[11], including:
Have a GitHub Issue in the k/enhancements[9] GitHub repository.
Has a merged KEP[10] in k/enhancements[9] GitHub repository that:
Is marked as "implementable"
Has a documented design
Has an updated test plan[4]
Has graduation criteria
Has an approved Production Readiness Review[2]
Additional Information
The tentative major milestones for the 1.25 release are the following:
Release Cycle begins — Monday, May 23rd, 2022
Production Readiness Review Soft Freeze — Thursday, June 9th, 2022
Enhancements Freeze — 18:00 PST on Thursday, June 16th, 2022
Code Freeze — 18:00 PDT on Tuesday, August 2nd, 2022
Test Freeze — 18:00 PDT on Tuesday, August 9th, 2022
Release Day — Tuesday, August 23rd, 2022
Full schedule — https://github.com/kubernetes/sig-release/tree/master/releases/release-1.25
Enhancements tracking sheet — https://bit.ly/k8s125-enhancements
Slack channels — #sig-release, #release-enhancements
If you have any questions, please do reach out! The process might seem complex but we're here to help.
Thanks,
Priyanka Saggu, 1.25 Enhancements Lead
[1]: https://bit.ly/k8s125-enhancements
[2]: https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md
[3]: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template
[4]: https://github.com/kubernetes/enhancements/commit/a86942e8ba802d0035ec7d4a9c992f03bca7dce9
[5]: https://groups.google.com/a/kubernetes.io/g/dev/c/6F3h0Z1QzVg
[6]: https://github.com/kubernetes/enhancements/pulls
[7]: https://groups.google.com/a/kubernetes.io/g/dev/c/2nSBeCWT_q0/m/NlH-qGbaBAAJ
[8] https://kubernetes.slack.com/archives/C02BY55KV7E
[9] https://github.com/kubernetes/enhancements
[10] https://github.com/kubernetes/enhancements/blob/master/keps/README.md
[11] https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template#release-signoff-checklist