-
Notifications
You must be signed in to change notification settings - Fork 39k
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
scope AWS LoadBalancer security group ICMP rules to spec.loadBalancerSourceRanges #63572
scope AWS LoadBalancer security group ICMP rules to spec.loadBalancerSourceRanges #63572
Conversation
/ok-to-test |
/assign @gnufied |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/cc @kubernetes/sig-aws-misc @countspongebob
/assign @justinsb |
/lgtm |
/ok-to-test |
/test pull-kubernetes-e2e-gce |
/assign @jsafrane |
/test pull-kubernetes-integration |
/lgtm - lets merge this. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: d-nishi, haz-mat, nckturner, timothysc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
@haz-mat |
/sig aws
What this PR does / why we need it:
Make the client CIDR ranges for MTU consistent with what the documentation appears to describe, where the ranges should be equal to
spec.loadBalancerSourceRanges
if supplied.Which issue(s) this PR fixes:
Fixes #63564
Release note: