-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fix restricted SG rules for named target port #2327
Conversation
3c84543
to
28a7219
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
[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 |
Issue
Fixes #2317
Description
With SG port restriction feature enabled, ingress model builder did not build the tgb networking configuration with the correct port when backend service port spec contained named ports. As a result, the security group did not have appropriate rules to allow backend traffic from the load balancer.
Testing
Added e2e tests to verify traffic in case of named target ports. The traffic tests failed in case of the old controller, and was successful with the new controller image.
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯