ingress-nginx: IP is not set on Ingress when using Multiple nginx Ingress controller in the same namespace

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

NGINX Ingress controller
  Release:       v1.1.1
  Build:         a17181e43ec85534a6fea968d95d019c5a4bc8cf
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.19.9

Kubernetes version (use kubectl version): v1.22.2

Environment:

• Cloud provider or hardware configuration: AKS
• Install tools: Terraform
• Basic cluster related info:

k version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:31:32Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-18T19:30:35Z", GoVersion:"go1.16.10",
Compiler:"gc", Platform:"linux/amd64"}
k get nodes
NAME                                   STATUS   ROLES   AGE   VERSION
aks-applications-18846254-vmss000000   Ready    agent   13d   v1.22.4
aks-applications-18846254-vmss000001   Ready    agent   13d   v1.22.4
aks-default-30170034-vmss000000        Ready    agent   13d   v1.22.4

• How was the ingress-nginx-controller installed:
  • If helm was used then please show output of helm ls -A | grep -i ingress

ingress-nginx           ingress-nginx           3               2022-02-02 08:57:07.025319779 +0000 UTC deployed        ingress-nginx-4.0.15    1.1.1
ingress-nginx-external  ingress-nginx      2               2022-02-02 10:08:11.601806206 +0000 UTC deployed        ingress-nginx-4.0.15    1.1.1

• If helm was used then please show output of helm -n <ingresscontrollernamepspace> get values <helmreleasename>

╰─ helm get  values ingress-nginx -n ingress-nginx
USER-SUPPLIED VALUES:
controller:
 autoscaling:
   enabled: true
   maxReplicas: 11
   minReplicas: 2
   targetCPUUtilizationPercentage: 1000
   targetMemoryUtilizationPercentage: 400
 config:
   log-format-escape-json: "true"
   log-format-upstream: '{ "@timestamp": "$time_iso8601", "network": {"forwarded_ip":
     "$http_x_forwarded_for"}, "client": {"ip": "$remote_addr"}, "user":{"name":
     "$remote_user"}, "user_agent":{"original": "$http_user_agent"}, "http":{ "version":
     "$server_protocol", "request":{ "body":{"bytes": $body_bytes_sent}, "bytes":
     $request_length, "method": "$request_method", "referrer": "$http_referer" },
     "response":{ "body": {"bytes": $body_bytes_sent}, "bytes": $bytes_sent, "status_code":
     "$status", "time": $request_time } }, "upstream": { "bytes": $upstream_response_length,
     "status_code":"$upstream_status", "time":$upstream_response_time, "address":
     "$upstream_addr", "name": "$proxy_upstream_name" }, "url_info":{ "domain":"$host",
     "path":"$uri", "query":"$args", "original":"$request_uri" } }'
   use-forwarded-headers: "true"
 ingressClassResource:
   controllerValue: k8s.io/internal-ingress-nginx
   default: false
   enabled: true
   name: internal-nginx
 resources:
   limits:
     cpu: 1000m
     memory: 2048Mi
   requests:
     cpu: 100m
     memory: 256Mi
 service:
   annotations:
     service.beta.kubernetes.io/azure-load-balancer-internal: "true"
   externalTrafficPolicy: Local
   labels:
     type: internal

╰─ helm get  values ingress-nginx-external -n ingress-nginx
USER-SUPPLIED VALUES:
controller:
 autoscaling:
   enabled: true
   maxReplicas: 5
   minReplicas: 2
   targetCPUUtilizationPercentage: 1000
   targetMemoryUtilizationPercentage: 400
 config:
   log-format-escape-json: "true"
   log-format-upstream: '{ "@timestamp": "$time_iso8601", "network": {"forwarded_ip":
     "$http_x_forwarded_for"}, "client": {"ip": "$remote_addr"}, "user":{"name":
     "$remote_user"}, "user_agent":{"original": "$http_user_agent"}, "http":{ "version":
     "$server_protocol", "request":{ "body":{"bytes": $body_bytes_sent}, "bytes":
     $request_length, "method": "$request_method", "referrer": "$http_referer" },
     "response":{ "body": {"bytes": $body_bytes_sent}, "bytes": $bytes_sent, "status_code":
     "$status", "time": $request_time } }, "upstream": { "bytes": $upstream_response_length,
     "status_code":"$upstream_status", "time":$upstream_response_time, "address":
     "$upstream_addr", "name": "$proxy_upstream_name" }, "url_info":{ "domain":"$host",
     "path":"$uri", "query":"$args", "original":"$request_uri" } }'
   use-forwarded-headers: "true"
 ingressClassResource:
   controllerValue: k8s.io/external-ingress-nginx
   default: false
   enabled: true
   name: external-nginx
 resources:
   limits:
     cpu: 1000m
     memory: 2048Mi
   requests:
     cpu: 100m
     memory: 256Mi
 service:
   annotations:
     service.beta.kubernetes.io/azure-load-balancer-internal: "false"
   externalTrafficPolicy: Local
   labels:
     type: external

• Current State of the controller: Both ingress controllers are healthy and detect when a new ingress is created

• Current state of ingress object, if applicable:

tyk         int-ing      internal-nginx   toto.internal.dns                           10.10.10.10     80, 443   6d16h
tyk         external-ing      external-nginx   toto.extern.dns                                                        80, 443   18h

For internal ingress controller it successfully assigned an IP address but not for external ingress controller

What happened: I don’t have any errors in both ingress controller, but for the external one it doesn’t assign any ip address whereas the Service is created as LoadBalancer type and a public ip is assigned. I can reach the service but External-dns is not able to create the record as no IP is assigned to my ingresses using external ingress controller. I tried to separate my ingress controller in two different namespace and it works

What you expected to happen: Did I miss something on the configuration of the ingress controller ? How to reproduce it: Create 2 nginx controller (with a different ingress-class) in the same namespace

Anything else we need to know: Example of ingress deployed

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/acme-challenge-type: dns01
    cert-manager.io/cluster-issuer: letsencrypt-dns-prod-nginx
  labels:
    app: test-ing2
    type: internal
  name: test-ing2
  namespace: default
spec:
  ingressClassName: internal-nginx
  rules:
    - host: test.internal.dns
      http:
        paths:
          - backend:
              service:
                name: svc
                port:
                  name: http
            path: /
            pathType: ImplementationSpecific
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/acme-challenge-type: dns01
    cert-manager.io/cluster-issuer: letsencrypt-dns-prod-nginx
  labels:
    app: test-ing
    type: external
  name: test-ing
  namespace: default
spec:
  ingressClassName: external-nginx
  rules:
    - host: test.externa.dns
      http:
        paths:
          - backend:
              service:
                name: svc
                port:
                  name: http
            path: /
            pathType: ImplementationSpecific