-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add an option to disable SG rules management for NLB #2481
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
Conversation
3cb8fee
to
789d7a8
Compare
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kishorj, M00nF1sh 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 |
@@ -46,6 +46,7 @@ | |||
| [service.beta.kubernetes.io/aws-load-balancer-alpn-policy](#alpn-policy) | stringList | | | | |||
| [service.beta.kubernetes.io/aws-load-balancer-target-node-labels](#target-node-labels) | stringMap | | | | |||
| [service.beta.kubernetes.io/aws-load-balancer-attributes](#load-balancer-attributes) | stringMap | | | | |||
| [service.beta.kubernetes.io/aws-load-balancer-manage-backend-security-group-rules](#manage-backend-sg-rules) | boolean | false | | |
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.
Isn't the default true?
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.
default is true, I'll fix the doc, thanks.
Issue
Fixes: #2358
Description
Provide a mechanism to configure SG rules management per service via the following annotation
If set to
"false"
, the controller will not add ingress rules to the EC2 instance/ENI security group for traffic and health check access. This feature is useful in case users have services with a lot of ports or multiple services and the individual SG ingress rules would hit the AWS SG rules quota. If disabled, users would have to add the rules for traffic and health check manually. If the annotation is not specified, the default value is"true"
.Manual tests
Created a service with the annotation
service.beta.kubernetes.io/aws-load-balancer-manage-backend-security-group-rules: "false"
, and verified the EC2 instance SG did not contain the ingress rules for the service ports.Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯