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

"internal" ingresses #138

Closed
caarlos0 opened this issue Feb 23, 2018 · 3 comments
Closed

"internal" ingresses #138

caarlos0 opened this issue Feb 23, 2018 · 3 comments

Comments

@caarlos0
Copy link

Hey!

Sorry if this is not the right place to ask or if I'm missing something, but, I wonder how can I create ingress with "internal" IPs (visible only inside the VPC)?

As far as I looked into, it only creates ingress with addresses like 35.x.x.x. I tried internal load balancers as well, which work, but there is 5 LB limit and I need a lot more than that.

Thanks!

@caarlos0 caarlos0 changed the title internal ingress "internal" ingresses Feb 23, 2018
@nicksardo
Copy link
Contributor

GCP does not have an internal HTTP(S) LB.

The HTTP(S) LB also utilizes backend services (I'm assuming you're seeing the quota of 5), so switching to L7 wouldn't help you. I recommend you go back to using the ILB and request more quota.

@kupson
Copy link

kupson commented Sep 13, 2019

It looks like GCP have internal HTTP(S) Load Balancers now - https://cloud.google.com/load-balancing/docs/l7-internal/setting-up-l7-internal

@MrHohn
Copy link
Member

MrHohn commented Sep 13, 2019

I believe this is happening. Ref #731.
cc @spencerhance

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

4 participants