You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.
This enhancement is targeting for stage stable for v1.30 (correct me, if otherwise)
Here's where this enhancement currently stands:
KEP readme using the latest template has been merged into the k/enhancements repo.
KEP status is marked as implementable for latest-milestone: 1.30.
KEP readme has up-to-date graduation criteria
KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).
The status of this enhancement is marked as Tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well, I couldn't find any related PR regarding this KEP in k/enhancements. Thank you!
Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.
I'd like to draw a little bit of attention to a related issue: kubernetes/apiextensions-apiserver#57. Perhaps it'll become easier to address once it's easier to have modules thanks to using workspaces.