Ingress controller with scoped ingress class validates ingress of other class about ingress-nginx HOT 5 OPEN

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from ingress-nginx.

/remove-kind bug
/kind support

I am almost certain that you need to check if both the controllers are different as per this example https://kubernetes.github.io/ingress-nginx/faq/#how-can-i-easily-install-multiple-instances-of-the-ingress-nginx-controller-in-the-same-cluster

from ingress-nginx.

@longwuyuan election and controllers are different, everything is already deployed and works.

Just these annoying error messages about validation of unrelated Ingress.
Well it is probably helpful for some people, but can it be turned off?

from ingress-nginx.

any chance you can show the cluster details in a screenshare ?

from ingress-nginx.

In any case I will mark it as a feature-request for this issue.

I tested and I see the message logged, once, at the time of creating a ingress resource, in the logs of the controller that does not own the ingressClass, of the newly created ingress resource.

The controllers watch all ingresses but only process the ingresses that are spec'd out with the ingressClass they own. This message to me is a info level log (need to check the code for exact spot) and there is no feature to optionally enable/disable such info log.

I guess if you are reporting then it must be impacting you but I am not inclined to expect that disabling this log message can be implemented in the near future, due to multiple reasons. Having it tracked here as a feature request seem the appropriate state for now.

from ingress-nginx.