-
Notifications
You must be signed in to change notification settings - Fork 301
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
Does/will the GCE ingress controller support whitelist-source-range? #38
Comments
From @nicksardo on April 6, 2017 17:59 The L7 Google Cloud Load Balancer does not currently have firewall rules for source IPs. I'll keep this open in case the load balancer supports it in the future. |
From @albertsun on April 28, 2017 17:6 This would be extremely useful to have. @nicksardo is there an open issue somewhere for the L7 LB to support source IP firewall rules where we can track the status of it? |
From @nicksardo on April 28, 2017 17:30 |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi, what is the status of this issue? We'd like to be able to control access to specific k8s services. This seems like the most likely way of handling it. Found this issue in google issue tracker: https://issuetracker.google.com/issues/35904903 |
It is still relevant. The bug tracker also receives +1s on a regular basis. |
Now that we have Cloud Armor and can restrict ingress based on IP, it would be interesting to incorporate Cloud Armor rules in ingress annotations. Is there a plan for that? |
@Slabber Cloud Armor integration with ingress-gce will be coming very soon :) |
/close |
@nicksardo - is a specific k8s version required to use the whitelist annotation? Or will it just start working for gce ingress? |
This is great news - thanks to everyone who has tracked and worked on this. |
Anyone was able to use the whitelist annotation in GCE ? |
Documentation for all our new feature support (IAP, CDN, CloudArmor) is available at https://cloud.google.com/kubernetes-engine/docs/concepts/backendconfig. I will work on a PR to add this same documentation to the README here. |
I know this is closed, but just wondering, is there any plan to support a whitelist/CloudArmor annotation at the ingress resource level? |
It's not a very good plan. It's too complicated |
From @nickform on April 6, 2017 12:11
Can anyone comment on when we will be able to use the 'whitelist-source-range' annotation with the GCE Ingress Controller? From Googling plus experimentation the answer is not "it works right now" but perhaps we've made a mistake? If not, is this something which might happen in future? Thanks!
Copied from original issue: kubernetes/ingress-nginx#566
The text was updated successfully, but these errors were encountered: