# Except for one, multiple ingress resources within the same namespace are not being assigned a load balancer IP by the ingress controller **URL:** \ **Category:** NGINX Ingress Controller\ **Tags:** config\ **Created:** [December 5, 2025, 11:59am UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473 "2025-12-05T11:59:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vinto007](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/vinto007/32/3894_2.png) [@vinto007](https://community.nginx.org/u/vinto007)\ **Post date:** [December 5, 2025, 11:59am UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/1 "2025-12-05T11:59:24Z")
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? ---
**Author:** ![AlexFenlon](https://avatars.discourse-cdn.com/v4/letter/a/3da27b/32.png) [@AlexFenlon](https://community.nginx.org/u/AlexFenlon)\ **Post date:** [December 8, 2025, 2:56pm UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/2 "2025-12-08T14:56:24Z")
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](https://github.com/nginx/kubernetes-ingress/tree/main/examples/ingress-resources/complete-example) 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](https://docs.nginx.com/nginx-ingress-controller/install/multiple-controllers/) might help. ---
**Author:** ![vinto007](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/vinto007/32/3894_2.png) [@vinto007](https://community.nginx.org/u/vinto007)\ **Post date:** [December 9, 2025, 2:04pm UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/3 "2025-12-09T14:04:20Z")
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](https://d7a5pgbt9tjl6.cloudfront.net/original/2X/3/3be1815ca1ac8169a9dbe722c4251c6b0853be64.png) ![image](https://d7a5pgbt9tjl6.cloudfront.net/original/2X/7/72e3908a7db986c8398d312d5b329b0db7d101b4.png) ![image](https://d7a5pgbt9tjl6.cloudfront.net/original/2X/2/23e2c229035220d44f61c77597be5715418a283f.png) I tried with 2 different versions like 2.3.1, 2.2.2 ---
**Author:** ![ve.patel](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@ve.patel](https://community.nginx.org/u/ve.patel)\ **Post date:** [December 10, 2025, 11:56am UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/4 "2025-12-10T11:56:09Z")
Hi @vinto007 , would you mind opening an issue [GitHub · Where software is built](https://github.com/nginx/kubernetes-ingress/issues) 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](https://github.com/nginx/kubernetes-ingress/tree/main/examples/ingress-resources/mergeable-ingress-types#mergeable-ingress-types-support) ```auto 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 ``` ---
**Author:** ![ve.patel](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@ve.patel](https://community.nginx.org/u/ve.patel)\ **Post date:** [December 23, 2025, 11:13am UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/5 "2025-12-23T11:13:51Z")
hi @vinto007 , was your issue resolved? ---
**Author:** ![system](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/system/32/19_2.png) [@system](https://community.nginx.org/u/system)\ **Post date:** [January 22, 2026, 11:14am UTC](https://community.nginx.org/t/except-for-one-multiple-ingress-resources-within-the-same-namespace-are-not-being-assigned-a-load-balancer-ip-by-the-ingress-controller/8473/6 "2026-01-22T11:14:40Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.