New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mutating Admission Policies #3962
Comments
/sig api-machinery |
/label lead-opted-in |
Hello @jpbetz @cici37 👋, Enhancements team here. Just checking in as we approach enhancements freeze on [02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca):. This enhancement is targeting for stage Here's where this enhancement currently stands:
I saw the comment here that a replacement KEP will be opened: #3963 (comment). Please link the new KEP as soon as it is available so we can properly assess whether it is ready for inclusion in the v1.30 release. The status of this enhancement is marked as |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hello @jpbetz 👋, 1.30 Docs Shadow here. ==== (non copy-pasted note: I'm pretty sure this requires docs! As it's an addition of a new alpha feature please remember to mark any docs you do write as alpha for version 1.30! |
👋 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. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
Hey again @jpbetz @cici37 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
After discussing with @cici37 @deads2k @fedebongio @alexzielenski, we'd like to re-target this enhancement for v1.31 milestone. We weighed the benefits of merging the first alpha in this release against the risks-- less than a week remaining till code freeze, high reviewer workloads and overall size of this enhancement. The quality of work so far is amazing, so part of our goal is to avoid "crunch" and the risks it entails. We feel it is best overall to take some extra time and merge this with a high level of quality and confidence in 1.31. We will continue to prioritize API and implementation review. Once the implementation PR is ready, we will hold it until the code thaws for 1.31 and then merge, hopefully early in the cycle. |
/milestone v1.31 |
Enhancement Description
k/enhancements
) update PR(s): [KEP 3962]MutatingAdmissionPolicy: alpha in 1.30 #4399k/k
) update PR(s):k/website
) update PR(s): [KEP-3962]Placeholder PR website#45248Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: