Server Side Apply: Unsetting Fields

[jpbetz]

Enhancement Description

-Server Side Apply: Unsetting Fields

• Kubernetes Enhancement Proposal: KEP-5051: Add Server Side Apply: Unsetting Fields KEP #5052
• Discussion Link:
• Primary contact (assignee):
  • @jpbetz
• Responsible SIGs:
  • sig-api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-5051: Add Server Side Apply: Unsetting Fields KEP #5052
  • Code (k/k) update PR(s):
    • KEP-5051: Add opt-in support for unset markers kubernetes-sigs/structured-merge-diff#280
  • Docs (k/website) update PR(s):

[jpbetz]

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

[jpbetz]

/sig api-machinery

[dipesh-rawat]

Hello @jpbetz 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage alpha for v1.33 (correct me, if otherwise)
/stage alpha

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: v1.33.
• 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would need to update the following:

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

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