Ideally, using kube-rs's admission controller will make it so we do not need to host Open API specification of the Configuration CRD as done in the current implementation.
Describe the solution you'd likekube-rs has good examples) for using their admission controller.
Additional context
This webhook was created initially for validating that the Configuration's components, namely that the broker PodSpec was properly formatted in the Configuration. It was made to catch formatting mistakes that would not be caught by serde serializing the configuration. Possibly, using the latest kube and k8s-openapi versions already solves this. See original issue: https://github.com/deislabs/akri/issues/180
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
Is your feature request related to a problem? Please describe. Now that we have updated to the latest
kube-rs
version in #361, we can take advantage ofkube-rs
's admission controller to simplify our Configuration Validating Webhook.Ideally, using
kube-rs
's admission controller will make it so we do not need to host Open API specification of the Configuration CRD as done in the current implementation.Describe the solution you'd like
kube-rs
has good examples) for using their admission controller.Additional context This webhook was created initially for validating that the Configuration's components, namely that the broker
PodSpec
was properly formatted in the Configuration. It was made to catch formatting mistakes that would not be caught by serde serializing the configuration. Possibly, using the latestkube
andk8s-openapi
versions already solves this. See original issue: https://github.com/deislabs/akri/issues/180