Issues with multiple ingress controllers not resolved by IngressClass spec

[deanb-everc]

What happened:

We have an EKS cluster version 1.21 , and we've deployed multiple ingress controllers through the official helm chart.
we recently ugpraded the chart version from 3.23.0 to 4.4.2 .
what happend is that all controllers were simultaneously racing to update Ingress status fields in confusing ways, same as described in this doc: https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/

What you expected to happen:

We added IngressClass under the spec field of the ingresses themselves. we expected the issue to be resolved, but it didn't.
So what we tried to do is adding the ingressclass as an annotation (the doc states that it will be deprecated) - this solved the issue. My question is - i assume this isn't the intended behavior. did anyone else experience a similar issue and can have information on what went wrong in the process?

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

NGINX Ingress controller
Release: v1.5.1
Build: d003aae
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.21.6

Kubernetes version (use kubectl version):

1.21

Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
  • Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
• Basic cluster related info:
  • kubectl version
  • kubectl get nodes -o wide

AWS EKS
cluster was created by terraform
uname -a: Linux mv-ingress-nginx-external-stageperf-controller-vwph7 5.4.228-132.418.amzn2.x86_64 #1 SMP Wed Jan 25 23:14:15 UTC 2023 x86_64 Linux

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm ls -A | grep -i ingress
  • If helm was used then please show output of helm -n <ingresscontrollernamepspace> get values <helmreleasename>
  • If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
  • if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances

• Current State of the controller:

  • kubectl describe ingressclasses
  • kubectl -n <ingresscontrollernamespace> get all -A -o wide
  • kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
  • kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>

• Current state of ingress object, if applicable:

  • kubectl -n <appnnamespace> get all,ing -o wide
  • kubectl -n <appnamespace> describe ing <ingressname>
  • If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag

• Others:

  • Any other related information like ;
    • copy/paste of the snippet (if applicable)
    • kubectl describe ... of any custom configmap(s) created and in use
    • Any other related information that may help

How to reproduce this issue:

Anything else we need to know:

[k8s-ci-robot]

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.

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/test-infra repository.

[longwuyuan]

/remove-kind bug Please try this https://kubernetes.github.io/ingress-nginx/user-guide/k8s-122-migration/#how-can-i-easily-install-multiple-instances-of-the-ingress-nginx-controller-in-the-same-cluster

…

On Tue, 28 Feb, 2023, 5:26 pm Kubernetes Prow Robot, < ***@***.***> wrote: 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. Instructions for interacting with me using PR comments are available here <https://git.k8s.io/community/contributors/guide/pull-requests.md>. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra <https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:> repository. — Reply to this email directly, view it on GitHub <#9678 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWTLC2IGBUWTF4ET2Q3WZXRW7ANCNFSM6AAAAAAVKT6JQU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[github-actions]

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 #ingress-nginx-dev on Kubernetes Slack.

[longwuyuan]

Please use this https://kubernetes.github.io/ingress-nginx/faq/#multiple-controller-in-one-cluster for multiple instances of the controller in the same cluster

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

Please use this https://kubernetes.github.io/ingress-nginx/faq/#multiple-controller-in-one-cluster for multiple instances of the controller in the same cluster

/close

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.