Declarative Validation Of Kubernetes Native Types With validation-gen

[aaron-prindle]

Enhancement Description

• One-line enhancement description (can be used as a release note): Implement declarative validation of Kubernetes native types using validation-gen to generate validation code.
• Kubernetes Enhancement Proposal: KEP 5073
• Discussion Link: KEP-5073: Declarative Validation of Kubernetes Native Types With validation-gen #5074
• Primary contact (assignee): @aprindle
• Responsible SIGs: sig-api-machinery
• Enhancement target (which target equals to which milestone):
  • Beta release target (x.y): 1.33
  • Stable release target (x.y):

Beta 1.34

• KEP ( k/enhancements ) update PR(s):
  • KEP-5073: Declarative Validation of Kubernetes Native Types With validation-gen #5074
  • KEP-5073: Declarative Validation: Explain and update document with cross-field validation information #5290
  • KEP-5073: Declarative Validation: Explain and update document with cross-field field reference validation information #5363
  • KEP-5073: Declarative Validation: Explain and update document with immutability validation information #5373
• Code ( k/k ) update PR(s):
  • Migrate to declarative validation - ReplicationController spec.replicas and spec.minReadySeconds fields: Migrate to declarative validation: ReplicationController spec.replicas and spec.minReadySeconds fields kubernetes#130725
  • Enable Declarative Validation for ReplicationController: Enable Declarative Validation for ReplicationController kubernetes#130724
  • add declarative validation metrics and associated runtime verification tests: [Declarative Validation] feat: add declarative validation metrics and associated runtime verification tests kubernetes#130705
  • Add default + optional handling: Declarative validation: Add default + optional handling kubernetes#130706
  • add Add CoveredByDeclarative to field error struct: [Declarative Validation] Add CoveredByDeclarative to field error struct kubernetes#130695
  • add feature gates: feat: add DeclarativeValidation and DeclarativeValidationMismatchMetric feature gates kubernetes#130478, [Declarative Validation] update Declarative Validation featuregate  kubernetes#130703
  • add validation-gen framework: KEP-5073: Declarative Validation: Add validation generator kubernetes#130349
  • chore(validation-gen): hold uniqueness check of listmap kubernetes#133038
  • feat: add CSR status.conditions approved+denied declarative validation tags to v1 and v1beta1 and add associated tests kubernetes#133013
  • feat(validation-gen): Add union validation rule tags and enable +k8s:item chaining to union tags kubernetes#133008
  • feat(validation-gen): add k8s:enum validators kubernetes#132823
  • feat(validation-gen): Enhance validation with new rules and core refactoring kubernetes#132469
  • fix: versioned validation test avoid incorrect conversion kubernetes#132465
  • Enable Declarative Validation for CertificateSigningRequest kubernetes#132361
  • feat(validation-gen): add default validation ratcheting support kubernetes#132236
  • feat(validation-gen): Improve validation test helpers for validation-gen kubernetes#132217
• Docs ( k/website ) update PR(s):
  • Declarative Validation Docs website: docs: add necessary feature gate information for KEP-5073 - Declarative Validation of K8s Native Types With validation-gen website#49732

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

[aaron-prindle]

/sig api-machinery
/wg api-machinery

[k8s-ci-robot]

@aaron-prindle: The label(s) wg/api-machinery cannot be applied, because the repository doesn't have them.

In response to this:

/sig api-machinery
/wg api-machinery

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jpbetz]

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

[lzung]

Hello @aaron-prindle 👋, 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 beta for v1.33 (correct me, if otherwise)
/stage beta

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