You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, AKS is the only major Kubernetes distribution that mutates ValidatingWebhookConfiguration and MutatingWebhookConfiguration unexpectedly to add additional namespaceNotIn label selectors for control-plane=true and kubernetes.azure.com/managedby=aks.
This behavior is causing countless issues for downstream apps:
and MANY more (just google admissions.enforcer/disabled and you will find hundreds)
Effectively, every major Kubernetes application has to work around this strange behavior so that customers of AKS can use the app, which is putting a large burden on the open-source community, and driving users away from Azure.
Describe the solution you'd like
My preference is that AKS removes the admission enforcer entirely, or at least disables it by default (with a strong warning that using it will likely break software designed for normal Kubernetes distributions).
If that is not possible, I would at the very least appreciate a new config to disable it at the cluster level, so I can recommend users of complex apps with many webhooks (like Kubeflow / deployKF), disable it to avoid all these problems.
Describe alternatives you've considered
Annotating every webhook with admissions.enforcer/disabled: "true", possibly by using another webhook.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently, AKS is the only major Kubernetes distribution that mutates
ValidatingWebhookConfiguration
andMutatingWebhookConfiguration
unexpectedly to add additional namespaceNotIn
label selectors forcontrol-plane=true
andkubernetes.azure.com/managedby=aks
.This behavior is causing countless issues for downstream apps:
admissions.enforcer/disabled
and you will find hundreds)Effectively, every major Kubernetes application has to work around this strange behavior so that customers of AKS can use the app, which is putting a large burden on the open-source community, and driving users away from Azure.
Describe the solution you'd like
My preference is that AKS removes the admission enforcer entirely, or at least disables it by default (with a strong warning that using it will likely break software designed for normal Kubernetes distributions).
If that is not possible, I would at the very least appreciate a new config to disable it at the cluster level, so I can recommend users of complex apps with many webhooks (like Kubeflow / deployKF), disable it to avoid all these problems.
Describe alternatives you've considered
Annotating every webhook with
admissions.enforcer/disabled: "true"
, possibly by using another webhook.The text was updated successfully, but these errors were encountered: