-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admission Webhook fined-grained request filtering (matchConditions) #11628
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Your issue description does not provide any info that has basic relevance. This link https://kubernetes.github.io/ingress-nginx/faq/#how-can-i-easily-install-multiple-instances-of-the-ingress-nginx-controller-in-the-same-cluster suggests how to use multiple instances of the controller so any problems on that is likely going to cause multiple reports about using more than one controller in same cluster. You can answer all the questions asked in the template of a new bug report by editing this issue description. If you actually copy/paste data from a kind cluster that is a proof of
because i can install 2 instances of the controller on one single kind cluster and not reproduce the problem you state |
/area helm |
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach |
Hey, one issue here might be, that your suggestion and the possibilities opposed by If someone would now manually add IngressClass resources, which is totally allowed, they could be taken into account by the Ingress Controller via their The current implementation of simply skipping non-matching Ingress resources in the controller might not be perfect, but it probably also isn't for other webhooks in a cluster and at least ensures all assigned IngressClass resources are always being considered. After all this is more of an issue of the Ingress API that hasn't changed in years and will be superseded by Gateway API. I therefore ask for your understanding and will close this issue now. Regards |
Thanks @Gacko for your reply. Your answer totally make sense when I read it twice 😃 . Many thanks for looking into it. |
What do you want to happen?
When running multiple instances of ingress-nginx with different
IngressClass
(e.g : external, internal) in the same cluster, the admission webhook configuration cannot currently condition calling one or the other webhook based on theIngressClass
.One workaround today is to use the webhook
ObjectSelector
condition (see here) and to label Ingresses accordingly (external / internal).Since Kubernetes v1.30, admission webhook can leverage the
matchConditions
statement (see here). This new feature allows for fine-grained request filtering based on the IngressClassName fieldℹ️ It would be interesting to add support for
matchCondition
in the ingress-nginx helm chartIs there currently another issue associated with this?
N/A
Does it require a particular kubernetes version?
Kubernetes v1.30 in stable (beta since v1.28)
The text was updated successfully, but these errors were encountered: