[URGENT] Upcoming Enhancements Deadline for v1.37

[Prajyot Parab]

Hello Kubernetes Community! 👋

Thank you everyone for the attention and cooperation with meeting PRR Freeze requirements! In nearly no time, we are now looking at the upcoming Enhancements Freeze, which is at the end of day Tuesday 16th June 2026 (Anywhere-on-Earth) / Wednesday 17th June 2026, 12:00 UTC.

This email is a final reminder for the Enhancements Freeze. Per our earlier PRR Freeze communication [0], all enhancements targeted for v1.37 should already be opted in and tracked on the Release tracking board [1].

If you have an enhancement opted-in to the release, please check the project board for the latest status:

• Tracked: means that the enhancement has met all criteria
• At Risk: means that the enhancement has NOT yet met all criteria

The release enhancements team is actively reviewing all outstanding
enhancements. Please ping your enhancements coordinator for more specific updates.

As a reminder: by enhancements freeze, we require that all enhancements in the release meet the following criteria:

• Have a GitHub Issue in the k/enhancements GitHub repository[2]
• Have a merged KEP in k/enhancements GitHub repository[2] that:
• Is marked as "implementable" for "latest-milestone: v1.37"
• Have all relevant sections of the KEP completed
• Have a test plan
• Have graduation criteria

Enhancements missing this deadline will require an exception[3].

Please note that, with KubeCon + CloudNativeCon India taking place on 18-19 June 2026[4], exception requests submitted after the Enhancements Freeze date may be subject to delayed review. Contributors are encouraged to keep this in mind when planning and submitting exception requests.

As of writing, we have 107 enhancements on the release tracking board:

• 39 "Tracked for Enhancement Freeze"
• 57 "At risk for Enhancement Freeze"
• 11 "Deferred" or "Removed from milestone"
  
  

Here is the breakdown of KEPs by SIG:

• api-machinery: 10
• apps: 3
• auth: 9
• autoscaling: 3
• instrumentation: 3
• network: 6
• node: 45
• scheduling: 16
• storage: 9
• etcd: 1
• cli: 1
• cloud-provider: 1

If your SIG is not listed here, it has not opted in for any enhancements for the v1.37 release.

If you need any clarification, please feel free to reach out in #release-enhancements on the Kubernetes Slack workspace[5].

Yours sincerely,

Prajyot Parab
Kubernetes v1.37 Release Lead Shadow

On behalf of the Kubernetes Release Team[6]

[0]: https://groups.google.com/a/kubernetes.io/g/dev/c/CCDOh-4Rb2E

[1]: v1.37 Release Tracking Board

[2]: https://git.k8s.io/enhancements

[3]: sig-release/releases/EXCEPTIONS.md

[4]: KubeCon + CloudNativeCon India 2026

[5]: Kubernetes Slack Workspace

[6]: sig-release/releases/release-1.37/release-team.md