Except for one, multiple ingress resources within the same namespace are not being assigned a load balancer IP by the ingress controller

Projects NGINX Ingress Controller
1

I am currently testing the migration from the ingress-nginx controller to the NGINX ingress controller. During testing, I noticed that, apart from one ingress resource, others in the same namespace are not being assigned a load balancer IP address and therefore are not working. If I delete the ingress that has an assigned IP, one of the other ingress resources starts working. How can we resolve this issue?

2

Hey @vinto007,

Thank you for taking the time to migrate over to NGINX Ingress Controller from ingress-nginx. We understand how annoying/tricky it might be coming over.

Can you check if ingressClassName is the same on all of the Ingress objects?

Make sure this is the same as what is described in the deployment.

Here is an example we have for an ingress, you can see that each ingress resource has a ingress class name matching the one of the pod.

This doc might help.

1 Like
3

Hi @AlexFenlon , I have the same ingressclass assigned for all of my ingress, but currently only one of the ingreess in the same namespace is working here is the screenshot for your reference. If I delete one which is working the other ingress will started working. Its looks wired for me..

image
image1873×268 18.9 KB

image
image706×100 7.66 KB

image
I tried with 2 different versions like 2.3.1, 2.2.2

4

Hi @vinto007 , would you mind opening an issue GitHub · Where software is built with kubectl describe output of your NGINX ingress controller deployment please and I’ll take a look.

Also try kubectl describe on your ingresses and check if there’s a host collisions warning, all Ingresses must have different hosts if they’re not mergeable ingresses

NAME            CLASS   HOSTS               ADDRESS       PORTS     AGE
cafe-ingress    nginx   cafe.example.com    xx.xx.xx.xx   80, 443   4m7s
cafe1-ingress   nginx   cafe1.example.com   xx.xx.xx.xx   80, 443   3m24s
cafe2-ingress   nginx   cafe2.example.com   xx.xx.xx.xx   80, 443   3m14s
cafe3-ingress   nginx   cafe3.example.com   xx.xx.xx.xx   80, 443   3m6s
5

hi @vinto007 , was your issue resolved?