1.22 Enhancements Update

[James Laverack]

Hi Kubernetes community!

We are now in week two of the Kubernetes 1.22 release, which means that enhancements freeze is just over a week away at 23:59:59 PST on Thursday the 13th of May.

The enhancements team has now reached out to each SIG via Slack to remind everyone of the opt-in process, the deadline, and confirming which enhancements are currently being tracked for each SIG.

Please remember that opting-in is only part of what is required, all enhancements must meet the following criteria by enhancements freeze:

• Have a GitHub Issue in the k/enhancements GitHub repository.
• Has a merged KEP in k/enhancements GitHub repository that:
• Is marked as "implementable"
• Has a documented design — or put another way must have all relevant sections of the KEP completed.
  
• Has a test plan
• Has graduation criteria
• Has an approved production readiness review

In addition, please note that the KEP template has been clarified to include a section for API and conformance tests on beta and GA graduations that contain API changes. Please check the latest KEP template for more details.

The enhancements team will begin reviewing KEPs this week, and will continue to do so up until enhancements freeze, so please watch out for comments from the team.

As of the time of writing we have 39 enhancements opt-ed in the release. This includes, by SIG:

SIG API Machinery: 2
SIG Apps: 6
SIG Auth: 3
SIG Cluster Lifecycle: 2
SIG Instrumentation: 4
SIG Network: 7
SIG Node: 4
SIG Storage: 9
SIG Windows: 2

(If a SIG is not listed above, then they have not yet opted any enhancements into the 1.22 release.)

And by Graduation type:

Alpha: 17
Beta: 12
GA/Stable: 9
Deprecation: 1

If you expect your enhancement to be opted in please check the tracking spreadsheet to verify it is present and tracked. If this is not the case then please reach out to your SIG to have it included ASAP!

Lastly, SIG leads will no longer be able to edit the tracking sheet after enhancements freeze. Any changes after that point will require an exception.

If you have any questions, please reach out to the enhancements team in #sig-release on Slack.

Thanks,

James Laverack, 1.22 Enhancements Lead