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
[release-1.28] feat: Add annotation service.beta.kubernetes.io/azure-allowed-ip-ranges
#4975
[release-1.28] feat: Add annotation service.beta.kubernetes.io/azure-allowed-ip-ranges
#4975
Conversation
Hi @lodrem. 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. Instructions 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/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lodrem, MartinForReal 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 |
8f40a2a
to
d7a0792
Compare
d7a0792
to
fcdaaa7
Compare
@lodrem Could you please squash the commit? |
0d0a309
to
71a1216
Compare
/retest |
1 similar comment
/retest |
@lodrem: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions 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/test-infra repository. |
/retest |
/ok-to-test |
/lgtm |
71a1216
to
5023364
Compare
/retest |
5023364
to
de79e7e
Compare
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Cherry pick #4762
This PR introduces a new annotation
service.beta.kubernetes.io/azure-allowed-ip-ranges
to manage the LoadBalancer service access. Previously, it was impossible to restrict access using both IP ranges and service tags (trying to usespec.loadBalancerSourceRanges
andservice.beta.kubernetes.io/azure-service-tags
together didn’t work as one might think). With these changes, we can useservice.beta.kubernetes.io/azure-allowed-ip-ranges
andservice.beta.kubernetes.io/azure-service-tags
simultaneously.Use cases:
limit access with both IP ranges and service tags
specify both
spec.loadBalancerSourceRange
and the new annotationspecify
spec.loadBalancerSourceRange
and service tags annotationWhich issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: