KEP-4008: CRDValidationRatcheting Exception Request

[Alexander Zielenski]

Hi everyone! 

I'd like to request an exception KEP in release 1.29

•    Enhancement name: CRDValidationRatcheting

•    Enhancement status (alpha/beta/stable): Alpha promoting to Beta
•    SIG: api-machinery
•    k/enhancements repo issue #: 4008
•    PR #’s:
    -    API Review: 121034
    -    Feature Gate bump: 121461
•    Additional time needed (in days): 3
•    Reason this enhancement is critical for this milestone:
    -    CRD Validation Rules going GA this release, to delay would mean adding a new field to its type immediately one release after GA graduation
•    Risks from adding code late: (to k8s stability, testing, etc.)
    -    Minor changes: order of 10s of non-testing lines not related to API field addition limited to CEL system in apiserver
•    Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
    -    Field added to stable validation rules API in 1.30 rather than during beta -> GA transition

The changes are ready and mainly blocked on reviewer bandwidth. Thank you!

[Priyanka Saggu]

Hi all,

Following discussion in Slack, the release team is APPROVING this exception request. Your updated deadline to merge all open code implementation PRs for your KEP is 18:00 PST Friday, 3rd November 2023.

If you need any clarification, please reach out to us in the #sig-release Slack channel.

Thanks,
Priyanka Saggu,
1.29 Release Team Lead

--
To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.