search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.33k stars 1.44k forks source link

Mutating Admission Policies #3962

Open jpbetz opened 1 year ago

jpbetz commented 1 year ago

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

kannon92 commented 1 year ago

/sig api-machinery

jpbetz commented 5 months ago

/label lead-opted-in /milestone v1.30

mickeyboxell commented 5 months ago

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 alpha for v1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

I saw the comment here that a replacement KEP will be opened: https://github.com/kubernetes/enhancements/pull/3963#issuecomment-1882318967. 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 at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

mickeyboxell commented 4 months ago

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

celestehorgan commented 4 months ago

Hello @jpbetz :wave:, 1.30 Docs Shadow here. 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. Thank you!

====

(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!

kcmartin commented 4 months ago

Hi @jpbetz, @cici37,

👋 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. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

mickeyboxell commented 4 months ago

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!

jpbetz commented 4 months ago

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.

jpbetz commented 4 months ago

/milestone v1.31

mickeyboxell commented 1 month ago

Hi @jpbetz 👋 v1.31 Enhancements team here.

I wanted to check in as we approach the enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting alpha for v1.31. Please correct me if that isn't the case.

Here's where this enhancement currently stands:

For this KEP, we need to do the following:

The status of this enhancement is marked as at risk for enhancement freeze. We can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

chanieljdan commented 3 weeks ago

Hi @jpbetz👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.

Thank you!

Daniel

mickeyboxell commented 3 weeks ago

Hi @jpbetz I wanted to follow up again prior to the enhancements freeze tomorrow. Do you think you'll have some time today or tomorrow to address the comments above?

dipesh-rawat commented 3 weeks ago

Hi @jpbetz 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze in few hours, at 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/3962#issuecomment-2148341607 that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

mickeyboxell commented 3 weeks ago

Hi @jpbetz 👋, v1.31 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

k8s-ci-robot commented 3 weeks ago

@mickeyboxell: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/kubernetes/enhancements/issues/3962#issuecomment-2167092128): >/milestone clear Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
sreeram-venkitesh commented 3 weeks ago

/milestone clear

sreeram-venkitesh commented 1 week ago

/label tracked/no