Skip to content

Commit f0a7c50

Browse files
authored
Merge pull request kubernetes#3948 from cici37/crdGA
KEP-2876: Clear Graduation Criteria for CRD validation rules to stable
2 parents 80e7686 + 5b9e61a commit f0a7c50

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

keps/sig-api-machinery/2876-crd-validation-expression-language/README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1134,8 +1134,10 @@ We plan to add e2e test under api-machinery for crd expression validation:
11341134

11351135
#### GA
11361136

1137-
- Formatted message. This targets in 1.27 and ideally should be in at least one release before going to GA.
1138-
- Scalability evaluation. Evaluate CRD scalability with validation rules against [previous scale target](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/95-custom-resource-definitions/README.md#scale-targets-for-ga).
1137+
- Formatted message. This has been added in 1.27.
1138+
- Scalability evaluation. Evaluate CRD scalability with validation rules against [previous scale target](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/95-custom-resource-definitions/README.md#scale-targets-for-ga). The evaluation is available [here](https://docs.google.com/document/d/1gU8FfBhKnkmzJUC32NmXMdh4vzbLxb-gkf52O9Un7Cg/edit?usp=sharing)
1139+
- Add optional fields reason and fieldPath into validation rules.
1140+
- Enable [CEL optional support](https://github.com/google/cel-spec/wiki/proposal-246) with proposed controlled rollout strategy. Ideally it should be in at least one release before going to GA.
11391141

11401142
## Production Readiness Review Questionnaire
11411143

keps/sig-api-machinery/2876-crd-validation-expression-language/kep.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ stage: beta
2727
# The most recent milestone for which work toward delivery of this KEP has been
2828
# done. This can be the current (upcoming) milestone, if it is being actively
2929
# worked on.
30-
latest-milestone: "v1.27"
30+
latest-milestone: "v1.28"
3131

3232
# The milestone at which this feature was, or is targeted to be, at each stage.
3333
milestone:

0 commit comments

Comments
 (0)