Feature: Support second nginx-ingress-controller for internal services
Created by: Nils98Ar
I think supporting a second ingress-controller for internal services like kubernetes-dashboard etc. that shouldn‘t be publicly accessible could be useful.
Access to the LoadBalancer service could be restricted via spec.loadBalancerSourceRanges at least if octavia load balancers are used.
IngressClass e.g. "nginx-internal": https://github.com/kubernetes/ingress-nginx/blob/8f54b538d9b32649411d9e507ca38fbee55ce51c/docs/user-guide/multiple-ingress.md?plain=1
It also needs to be considered which ingress controller should be the default one if no IngressClass is provided in an ingress resource.