Promoting feature CustomResourceValidationExpressions to beta

[cici37]

The feature has been promoted to beta in Kubernetes 1.25. Here is the doc update.
KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/2876-crd-validation-expression-language/README.md

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	d6201fd
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/62fbba1c4510430008c2a7a3

[sftim]

/retitle [WIP] Placeholder pr for promoting feature CustomResourceValidationExpressions to beta

This is a placeholder and is not ready for review.

[reylejano]

This PR is for enhancement kubernetes/enhancements#2876 which is being tracked for the 1.25 release
@cici37 , when this PR is ready for review, please remove [WIP] from the title
/milestone 1.25
/assign @didicodes
/cc @kcmartin

[cici37]

/cc @jpbetz Would you have time to take a look? Thank you

[cici37]

/retest

[sftim]

Thanks for this PR @cici37

For graduation to beta, we'd really like to see documentation that follows the usual docs layout.

Please propose an update so that https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ includes a clear mention of validation rules, along with brief details of how to disable them.

You could adapt the existing task content. I also recommend adding a task page that explains how to define validation and transition rules for a custom API - but it's OK for that to land in main any time before the v1.26 release.

[cici37]

Thanks for this PR Cici Huang

For graduation to beta, we'd really like to see documentation that follows the usual docs layout.

Please propose an update so that https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ includes a clear mention of validation rules, along with brief details of how to disable them.

You could adapt the existing task content. I also recommend adding a task page that explains how to define validation and transition rules for a custom API - but it's OK for that to land in main any time before the v1.26 release.

Thank you for reviewing! I have added the info on how to turn off the feature. Would you mind to take a look when have time? Thank you

[sftim]

/lgtm

I'd prefer a couple more tweaks (see inline feedback).

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f9c27b5c4ac059fa2c7fbaab1a4f77576cc57aa2

[reylejano]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: reylejano

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [reylejano]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[reylejano]

Reapplying lgtm from this comment
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 14fe02c1cd3a60b940c55bc7743e7db6bc3b487f

[sftim]

Relevant to #35991

Ideally: we'd have got the docs sorted ahead of the beta; we should definitely instead get those updated on main well ahead of this feature being proposed for stabilization.