AdmissionWebhook isn't scoped by Ingress Class #7759
Labels
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
v1.0.2
Kubernetes version (use
kubectl version
):Environment:
Cloud provider or hardware configuration: AWS EKS 1.19
OS (e.g. from /etc/os-release): AmazonLinux2
Kernel (e.g.
uname -a
): unsureInstall tools:
Please mention how/where was clsuter created like kubeadm/kops/minikube/kind etc.
Basic cluster related info:
kubectl version
: v1.19.15helm version
:version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.17"}
How was the ingress-nginx-controller installed:
helm ls -A
helm -n <ingresscontrollernamepspace> get values <helmreleasename>
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
What happened:
When creating 2 ingresses with the same Host and Path values, but with different ingress classes, the admission webhook returns an error.
What you expected to happen:
The admission webhooks should be scoped to their respective ingress class.
How to reproduce it:
Anything else we need to know:
/kind bug
The text was updated successfully, but these errors were encountered: