CRD Validation Expression Language

[jpbetz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Expression language can be used to validate custom resources
• Kubernetes Enhancement Proposal: KEP-2876: CRD Validation Expression Language #2877
• Discussion Link: SIG API Machinery Agenda Item
• Primary contact (assignee): cici37, jpbetz
• Responsible SIGs: sig-api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23, 1.24
  • Beta release target (x.y): 1.25
  • Stable release target (x.y): 1.29
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    • Add wired off code for Validation rules for Custom Resource Definitions using the CEL expression language kubernetes#106234
    • Feature implementation: Validation rules for Custom Resource Definitions using the CEL expression language kubernetes#106051
  • Docs (k/website) update PR(s):
    • Add documentation for Validation Rules feature to Custom Resource Definitions task docs website#30626
• Beta
  • KEP (k/enhancements) update PR(s): KEP-2876: Promote CRD Validation Expression Language to Beta #3266
  • Code (k/k) update PR(s):
    • Promote feature CustomResourceValidationExpressions to beta kubernetes#111524
    • Add messageExpression field for CRD validation kubernetes#115969
  • Docs (k/website) update PR(s):
    • Promoting feature CustomResourceValidationExpressions to beta website#35029
    • Documentation for messageExpression update to KEP-2876 website#40019
• Bate in 1.28
  • KEP (k/enhancements) update PR(s): KEP-2876: Clear Graduation Criteria for CRD validation rules to stable #3948
  • Code (k/k) update PR(s): [KEP-2876]Add reason and fieldPath into CRD validation rules kubernetes#118041
  • Docs (k/website) update(s):
    • [KEP-2876] Placeholder doc PR for kep 2876 website#42043
    • Update doc for KEP 2876 website#42120
• Stable
  • KEP (k/enhancements) update PR(s): [KEP-2876]Promote CRD validation rule to stable #4159
  • Code (k/k) update PR(s): [KEP-2876] Promote CRD validation rule to GA kubernetes#121373
  • Docs (k/website) update(s): [KEP-2876] Document (GA) CEL validation for custom resources website#43441

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

[mysunshine92]

/sig api-machinery

[kevindelgado]

Hi @jpbetz and @cici37! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo (PR Open).
• KEP status is marked as implementable
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria (Only has criteria for beta).
• KEP has a production readiness review that has been completed and merged into k/enhancements.

If you can, please add a test plan and alpha graduation criteria to the KEP and be sure the KEP PR merges by enhancements freeze :)

Thanks!

[kevindelgado]

/milestone 1.23
/stage alpha

[k8s-ci-robot]

@kevindelgado: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.23
/stage alpha

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/test-infra repository.

[kevindelgado]

/milestone v1.23

[kevindelgado]

Hi @cici37

Ping! As a reminder your PR (#2877) needs to merge by EOD PST tomorrow September 9th to be included in the 1.23 Release. After that time you will need to request an exception.

Lmk if you need anything,
Kevin

[cici37]

@kevindelgado PR has been merged. Updated the checkbox. Thanks^^

[mehabhalodiya]

Hi @jpbetz 👋 1.23 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!