Issue with deployed rke2 second Ingress-Nginx Controller inside a Kubernetes cluster running on bare-metal.

[Ganesh-hub-5]

We have deployed two Nginx ingress controller in our cluster. The first ingress controller works fine but we are facing issue with second one. When accessing the service through second ingress controller (http://x3.abc.com/sample), we get This site can’t be reached x3.abc.com took too long to respond. error. We followed the same step as the first ingress controller including assigning different IP address using metallb and different ingress class in different namespace.

Details:
RKE2 Version: v1.28.11
Kubernetes Version: Client Version: v1.30.3 Server Version: v1.28.11
NGINX Ingress controller
Release: v1.10.1-hardened1
Build: git-b48c66a2f
Repository: https://github.com/rancher/ingress-nginx
nginx version: nginx/1.25.3

Metallb Version: v0.14.5

For testing purpose we deployed a simple nginx image using below yaml files. Everything is up and running, No error logs in pods
, service mapped correct endpoints and ingress resource got external IP assigned by Second nginx ingress controller But when we try to access http://x3.abc.com/sample gives Site can't be reached error.
Deployment.yaml

Service.yaml

Ingress.yaml

When we change ingress class and host of the ingress resource with First ingress controller rest everything same then service is accessible via http://y3.abc.com/sample gives Welcome to Nginx

Ingress2.yaml

we would appreciate it if someone could help us to find out root cause of this issue. I am ready to provide any additional details if required. Thanks in advance!!

[j1m-ryan]

Hi @Ganesh-hub-5, I believe you are referring to the community ingress controller based on your annotations and ingress controller version. This is a separate project to this so you can make an issue there for it.