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

Support use of field spec.loadBalancerSourceRanges on Services of type LoadBalancer #122

Closed
julianvmodesto opened this issue May 25, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@julianvmodesto
Copy link
Contributor

commented May 25, 2017

AWS, GCE and GKE support use of the spec.loadBalancerSourceRanges field on Services of type LoadBalancer to configure the firewall for the load balancer created by Kubernetes.

apiVersion: v1
kind: Service
metadata:
  annotations:
    ingress.appscode.com/name: frontend
    ingress.appscode.com/type: LoadBalancer
  name: voyager-frontend
spec:
...
  type: LoadBalancer
  loadBalancerSourceRanges:
  - 130.211.204.1/32
  - 130.211.204.2/32

https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/

@julianvmodesto

This comment has been minimized.

Copy link
Contributor Author

commented Jun 15, 2017

Just a heads up that there's an upstream issue with spec.loadBalancerSourceRanges:

kubernetes/kubernetes#34218

@tamalsaha tamalsaha reopened this Jun 15, 2017

@julianvmodesto

This comment has been minimized.

Copy link
Contributor Author

commented Jun 15, 2017

Not an issue with voyager, just upstream :) but might cause confusion if anyone runs into this

@tamalsaha

This comment has been minimized.

Copy link
Member

commented Jun 15, 2017

Yeah. I am going to note this in changelog for 1.5.6. Thanks!

@tamalsaha tamalsaha closed this Jun 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.