Added support for IP range blocking rules#9833
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Welcome @tomjankovec! |
|
Hi @tomjankovec. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tomjankovec The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ada6797 to
a6248f1
Compare
5d8b710 to
3a4993b
Compare
|
/ok-to-test |
|
/kind feature |
Liunardy
left a comment
There was a problem hiding this comment.
Please update the PR description since it seems outdated, looking at how it says:
The implementation validates that
allowed-ip-rangesandblocked-ip-rangescannot be used together
Liunardy
left a comment
There was a problem hiding this comment.
Could you add E2E test(s) for the block IP ranges functionality?
added |
fixed |
What type of PR is this?
/kind feature
What this PR does / why we need it:
The PR adds support for IP range blocking, which is needed to facilitate network traffic denial on a load balancer level.
This contribution adds a new
service.beta.kubernetes.io/azure-blocked-ip-rangesannotation for denying traffic from specific IP ranges to Azure Load Balancer services.Blocked IP deny rules use a dedicated priority range (400-499), ensuring they're evaluated before allow rules (500+). The implementation supports both IPv4 and IPv6, and includes comprehensive tests—including a test confirming that exceeding 100 blocking rules returns a priority exhaustion error.
Does this PR introduce a user-facing change?
NONE