Enabling publish-service for ClusterIP nginx-ingress controller service
Currently, nginx-ingress controller can be run as a ClusterIP type service, however, it does not allow publishing this service’s endpoints to associated ingress objects. As a result, external-dns is not able to detect these ingress objects without any IP Address to create/update A DNS records for them. Why? Many may argue that why will someone need DNS records for ingress objects using ClusterIP type nginx-ingress service. They aren’t reachable from outside the kubernetes cluster, anyways....