nginx-ingress unable to publish endpoints to ingress when using ClusterIP type controller service

[rtnpro]

Is this a request for help?
No

What keywords did you search in NGINX Ingress controller issues before filing this one?

ClusterIP publish service

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT

NGINX Ingress controller version:

0.25

Kubernetes version (use kubectl version):

v1.14.3

Environment:

• Cloud provider or hardware configuration: DigitalOcean
• OS (e.g. from /etc/os-release): Debian GNU/Linux 9 (stretch)
• Kernel (e.g. uname -a): 4.19.0-0.bpo.5-amd64
• Install tools: DigitalOcean managed Kubernetes
• Others:

What happened:

When I run nginx-controller behind ClusterIP type service along with enabling publish-service for the ClusterIP nginx-controller service, the nginx-ingress controller fails to publish the service's endpoint to the associated ingress. With endpoints missing for an ingress object, external-dns fails to create DNS records for these ingresses.

What you expected to happen:

Even if the nginx-controller service is of type ClusterIP, when --publish-service is enabled, it should publish the private IP for the service to the associated ingress objects.

How to reproduce it (as minimally and precisely as possible):

• Install nginx-ingress via helm with values like

controller:
  image:
    repository: quay.io/kubernetes-ingress-controller/nginx-ingress-controller
    tag: "0.25"
  ingressClass: internal-ingress
  publishService:
    enabled: true
  replicaCount: 1
  resources:
    requests:
      cpu: 100m
      memory: 100Mi
    limits:
      memory: 256Mi

  service:
    type: ClusterIP

• Deploy an app with ingress using internal-ingress as the ingress class. It will not receive any endpoint from the nginx-controller service.

Here are artifacts from my Kubernetes cluster to reproduce this bug:

• nginx-ingress Deployment: https://gist.github.com/rtnpro/6711b6ed11fcd7162508f43fd2c330eb#file-deployment-internal-ingress-nginx-ingress-controller-yaml
• nginx-ingress-controller service: https://gist.github.com/rtnpro/6711b6ed11fcd7162508f43fd2c330eb#file-svc-internal-ingress-nginx-ingress-controller-yaml
• ingress: https://gist.github.com/rtnpro/6711b6ed11fcd7162508f43fd2c330eb#file-ing-internal-app-yaml

Anything else we need to know: