Merge pull request #4225 from cici37/vapGA

[KEP-3488]Promote ValidatingAdmissionPolicy to GA

Author: k8s-ci-robot

keps/prod-readiness/sig-api-machinery/3488.yaml

@@ -3,3 +3,6 @@ alpha:
   approver: "@johnbelamaric"
 beta:
   approver: "@johnbelamaric"
+stable:
+  approver: "@johnbelamaric"
+

keps/sig-api-machinery/3488-cel-admission-control/README.md

@@ -2404,7 +2404,14 @@ in back-to-back releases.
 - support the list of features mentioned under phrase 2
 
 ## GA
-- complete type check for CRD and aggregated types
+- Complete type check for CRD and aggregated types
+- Scalability evaluation. Evaluate ValidatingAdmissionPolicy scalability including how many validators it could run, runtime cost evaluation, evaluating the reasonable ResourceQuota for
+  ValidatingAdmissionPolicy, how much faster comparing with Webhook, the scale target, etc.
+- Fix the known issues along the way([variables should keep the type info](https://github.com/kubernetes/kubernetes/issues/120239), [variables should mark omitempty](https://github.com/kubernetes/kubernetes/issues/120491), [properly escape](https://github.com/kubernetes/kubernetes/issues/118230), [reconsilition with api-server restart](https://github.com/kubernetes/kubernetes/issues/122658))
+- Get agreement on the excluded resources in [this issue](https://github.com/kubernetes/kubernetes/issues/122205).
+- Define the mechanism for CEL library update policy after GA(version skew policy, the policy to update CEL library, etc). Sync with Declarative Validation on CEL libraries to prevent unexpected libraries be added after GA. Provide documentation on library change.
+- Adoption: at least two organizations have demonstrated it is useful for major use cases.
+- Have enough test coverage for common use cases and corner use cases.
 
 ### Upgrade / Downgrade Strategy
 

keps/sig-api-machinery/3488-cel-admission-control/kep.yaml

@@ -33,17 +33,18 @@ see-also:
   - "/keps/sig-api-machinery/2876-crd-validation-expression-language"
 
 # The target maturity stage in the current dev cycle for this KEP.
-stage: beta
+stage: stable
 
 # The most recent milestone for which work toward delivery of this KEP has been
 # done. This can be the current (upcoming) milestone, if it is being actively
 # worked on.
-latest-milestone: "v1.29"
+latest-milestone: "v1.30"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
   alpha: "v1.26"
   beta: "1.28"
+  stable: "1.30"
 
 
 # The following PRR answers are required at alpha release