What would you like to be added:
Validating Admission Policy has been alpha since 1.26 and it graduated to beta in Kubernetes 1.28.
We would like to start to use it on our EKS-A clusters.
Why is this needed:
To be able to use a Kubernetes native feature for admission controller. While there are existing 3rd party solutions like Kyverno, OPA/Gatekeeper, Datree, these tools need to be maintained by the platform admins and some of them have very steep learning curve (rego).
While Validating Admission Policy may not be a fit for all use cases (no external context during decision making) it is definitely provides enough flexibility to cover most of the use cases that a kubernetes platform require.
What would you like to be added: Validating Admission Policy has been alpha since 1.26 and it graduated to beta in Kubernetes 1.28. We would like to start to use it on our EKS-A clusters.
Why is this needed: To be able to use a Kubernetes native feature for admission controller. While there are existing 3rd party solutions like Kyverno, OPA/Gatekeeper, Datree, these tools need to be maintained by the platform admins and some of them have very steep learning curve (rego). While Validating Admission Policy may not be a fit for all use cases (no external context during decision making) it is definitely provides enough flexibility to cover most of the use cases that a kubernetes platform require.