Mutating Admission Policies

[jpbetz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Introduce CEL based Mutating Admission Policies
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3962-mutating-admission-policies
• Discussion Link: https://groups.google.com/g/kubernetes-sig-api-machinery/c/VY1oAl7a6nU
• Primary contact (assignee): jpbetz, cici37
• Responsible SIGs: API Machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.34
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • [KEP 3962]MutatingAdmissionPolicy: alpha in 1.30 #4399
    • KEP-3962: Mutating Admission Policies - update for 1.32 #4917
  • Code (k/k) update PR(s):
    • KEP-3962: MutatingAdmissionPolicy Alpha kubernetes#127134
  • Docs (k/website) update PR(s): KEP-3962: Mutating admission policy documentation website#48646
• Beta 1.34
  • KEP (k/enhancements) update PR(s): [KEP-3962]Promote MAP to beta in 1.34 #5251
  • Code (k/k) update PR(s): [KEP-3962]Promote MutatingAdmissionPolicy to Beta kubernetes#132821
  • Docs (k/website) update(s): [KEP-3962]Update the status of the MutatingAdmissionPolicy website#51534

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

[kannon92]

/sig api-machinery

[jpbetz]

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

[mickeyboxell]

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:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: { CURRENT_RELEASE }. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• 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).

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 at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!