Restrict CIDR ip addresses for a LoadBalancer type service #614
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was changed
Restrict IP addresses for load balancers created for the frontend service by adding the
spec.loadBalancerSourceRanges
for the LoadBalancer type.Why?
I am self-hosting temporal on a Google Kubernetes Engine (GKE) cluster running temporal workflows. I have exposed the frontend service as an internal load balancer to my Cloud Run service (which initiates the temporal workflows) but, by default, the firewall rule created by the GKE service sets a source as "0.0.0.0/0". I am required to further restrict the allowed source ip range to specific subnets.
GCP guide about restricting ip addresses based on CIDRs in
spec.loadBalancerSourceRanges[]
. Additionally, AWS documentation states thatspec.loadBalancerSourceRanges[]
is used to restrict IP addresses.Checklist
output is
server.frontend.service.loadBalancerSourceRanges
from my helm values.yaml file.No