publish-service argument isn't honored when ELB is internal only facing.

[snoby]

Using version 0.9.0.beta3 of the nginx ingress controller. I have the following command arguments for my ingress controller:

    spec:
      containers:
      - args:
        - /nginx-ingress-controller
        - --default-backend-service=$(POD_NAMESPACE)/nginx-default-backend
        - --configmap=$(POD_NAMESPACE)/internal-ingress-nginx
        - --publish-service=$(POD_NAMESPACE)/internal-ingress-nginx
        - --ingress-class=internal
        - --healthz-port=10001

along with a service definition with annotations that look like:

  annotations:
    service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: '*'
    service.beta.kubernetes.io/aws-load-balancer-internal: '0.0.0.0/0'

The problem is that it doesn't look like the "publish-service" option is being honored when the load balancer is internal. This works perfectly fine when the load balancer is an internet facing ELB.

[aledbf]

@snoby what is the issue exactly? The ingress controller just uses the service, there is no interaction with the aws configuration or API.

[janwillies]

for me the setup works fine with 0.9.0-beta.7

[aledbf]

Closing. Please reopen if still have issues with the latest beta.