1.32 Enhancements Update

[Tyler Schade]

Hello, Kubernetes community!

We are now in week four of the Kubernetes 1.32 release cycle, which means that the Enhancements Freeze is just a week away on 02:00 UTC Friday, October 11th, 2024 / 19:00 PDT Thursday, October 10th, 2024, as announced recently.

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

Please remember that opting-in is only the first part of what is required. All enhancements must meet the following criteria by the time the enhancements freeze rolls around:

• Have a GitHub Issue in the k/enhancements GitHub repository.
  

• Has a merged KEP in k/enhancements GitHub repository that:
  

  • Is marked "implementable"
    

  • Has a documented design — or put another way, it must have all relevant sections of the latest KEP template completed.
    

  • Has a test plan
    

  • Has graduation criteria
    

  • Has an approved production readiness review

The enhancements team has begun reviewing KEPs, 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 72 enhancements opt-ed in the release.

These include (by SIG):

SIG Api-machinery: 6

SIG Apps: 3

SIG Auth: 10

SIG CLI: 2

SIG Instrumentation: 2

SIG Network: 5

SIG Node: 34

SIG Scheduling: 3

SIG Storage: 5

SIG Storage: 21

SIG Windows: 2

(If a SIG is not listed above, then they have not yet opted for any enhancements into the 1.32 release, as of October 2nd, 2024.)

And by Graduation type:

Alpha: 35

Beta: 14

GA/Stable: 21

Deprecation: 1

If you expect your enhancement to be opted in please check the 1.32 Enhancements tracking board 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 add KEPs to the tracking board. Any changes after that point will require an exception.

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

Thanks!

Tyler Schade, 1.32 Enhancements Lead