Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
snoby opened this issue Apr 25, 2017 · 3 comments
Closed

Comments

@snoby
Copy link

snoby commented Apr 25, 2017

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
Copy link
Member

aledbf commented Jun 15, 2017

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

@janwillies
Copy link

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

@aledbf
Copy link
Member

aledbf commented Jun 16, 2017

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

@aledbf aledbf closed this as completed Jun 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants