Re: Enhancement freeze exception request - KEP 5073 - Declarative Validation Of Kubernetes Native Types With validation-gen

28 views
Skip to first unread message

Aaron Prindle

unread,
Feb 14, 2025, 3:19:59 AM (12 days ago) Feb 14
to kubernetes-sig...@googlegroups.com, kubernetes-...@googlegroups.com, releas...@kubernetes.io

* Reason this enhancement is critical for this milestone: No reason, but

it is a straightforward enhancement that was completed with appropriate review (Sig Lead + PRR) but the KEP was missing the "Release Signoff Checklist" section in the initial submission which is actively being rectified with: https://github.com/kubernetes/enhancements/pull/5171


On Thu, Feb 13, 2025 at 7:08 PM Aaron Prindle <apri...@google.com> wrote:

Hi all,


I would like to request an exception on feature freeze for [KEP-5073] Declarative Validation Of Kubernetes Native Types With validation-gen to be promoted to Beta. The feature risk is low and very specific to a small number of kubernetes resource validation rules for a small number of fields (likely 2-5) for a small number of k8s resource(s) (likely 1)  for 1.33.


The KEP is already approved by an api-machinery SIG Lead (thanks David Eads!),

PRR reviews (thanks Joe Betz!) and merged, targeting v1.33.


Thanks!

=======

Enhancement name: Declarative Validation Of Kubernetes Native Types With validation-gen

Enhancement status (alpha/beta/stable): beta

SIG: api-machinery

k/enhancements repo issue #: #5073

PR #’s: https://github.com/kubernetes/enhancements/pull/5074 (already

approved by SIG and PRR reviewer and merged)

Additional time needed (in days): 1 (PR for KEP is already merged)

Reason this enhancement is critical for this milestone: No reason, but

it is a bare simple enhancement that w

Risks from adding code late: (to k8s stability, testing, etc.): low

risk, the enhancement touches a small number of fields part in validation code in lesser used k8s resources.

Risks from cutting enhancement: (partial implementation, critical

customer usecase, etc.): foundational to future work related to making kubernetes API reviews easier, improving kubernetes API validation and helping users create new kubernetes APIs.



Aaron Prindle

unread,
Feb 14, 2025, 3:19:59 AM (12 days ago) Feb 14
to kubernetes-sig...@googlegroups.com, kubernetes-...@googlegroups.com, releas...@kubernetes.io

David Eads

unread,
Feb 14, 2025, 2:53:50 PM (11 days ago) Feb 14
to Aaron Prindle, kubernetes-sig...@googlegroups.com, kubernetes-...@googlegroups.com, releas...@kubernetes.io
I approve/endorse this exception.  The KEP and PRR were agreed and merged prior to the deadline, but we forgot to complete the checklist.  Checklist corrected in https://github.com/kubernetes/enhancements/pull/5171.

--
You received this message because you are subscribed to the Google Groups "K8s API Machinery SIG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-api-m...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-api-machinery/CAOdApdUsNA49fRYUGneTiV1wEt74_mZnUyHM5xnKwS2DENQZpQ%40mail.gmail.com.

Nina Polshakova

unread,
Feb 14, 2025, 3:55:02 PM (11 days ago) Feb 14
to kubernetes-sig-release
Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge all PRs for your KEP is 8:00 PDT on Saturday, 15th February 2025.

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

Thanks,
Nina Polshakova
1.33 Release Team Lead

Reply all
Reply to author
Forward
0 new messages