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

Specifying the loadBalancerIP used by the Ingress #131

Closed
paultiplady opened this issue Jan 15, 2017 · 3 comments
Closed

Specifying the loadBalancerIP used by the Ingress #131

paultiplady opened this issue Jan 15, 2017 · 3 comments

Comments

@paultiplady
Copy link

I'd like to use a static IP for my ingress. Currently, the Nginx Ingress Controller allocates a new loadBalancerIP each time it starts.

For Services, it's possible to pin the IP using loadBalancerIP: 1.2.3.4. Is this possible in the Nginx Ingress Controller?

If not, is there some other approach that can be used to pin the IP of an Ingress?

(Copied from contrib issue kubernetes-retired/contrib#2221)

@aledbf
Copy link
Member

aledbf commented Jan 15, 2017

@paultiplady you can use the new flag publish-service to use an existing service (with type=LoadBalancer)

@timrsmith
Copy link

timrsmith commented Jan 26, 2017

@aledbf Can this be done with ssl-passthrough? We currently have ingress with the following:

annotations:
  kubernetes.io/ingress.class: nginx
  ingress.kubernetes.io/ssl-passthrough: 'true'

We were trying to determine how to specify a static ip for the ingress, so this sounds promising but I'm unclear on how the LoadBalancer service works in concert with the ingress and ingress controller in this scenario.

@aledbf
Copy link
Member

aledbf commented Jun 16, 2017

Closing. Please use the flag --publish-service. Reopen if you still have issues.

@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