-
Notifications
You must be signed in to change notification settings - Fork 1k
Closed
Description
Misconfigured or misbehaving webhooks are an ongoing source of problems see:
- Admission Webhook prevents Kubeflow pod deployment. kubeflow#4808
- Uber Issue: KFServing admission hook causing widespread issues because its a global admission hook kserve/kserve#568
- Katib webhooks blocking pod creation in kubeflow namespace katib#1261
In #1213 we started adding testing to verify that webhooks are well behaved.
However, this only works if an application configures webhooks explicitly as part of its kustomize package.
We have at least two applications (katib, and kfserving) in which the webhooks are dynamically and automatically created. This has a couple disadvantages
- Operator doesn't know beforehand what resources will be created
- Operator has no way to customize the webhooks if needed
- Controllers need sufficient RBAC permissions to create webhooks
Should we recommend or require that all applications support at least optionally explicit creation of their webhooks and provide YAML resources to do so?
Should we enforce that by adding tests similar to #1213 to disallow RBAC permissions to create webhooks?
/cc @andreyvelich @johnugeorge @ellistarn @yuzisun @cliveseldon @animeshsingh
peterupton