-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
#5700: Add command line flag for disabling Subnet ELB tags #5875
#5700: Add command line flag for disabling Subnet ELB tags #5875
Conversation
e0a906e
to
ca073d0
Compare
/assign @andrewsykim |
ca073d0
to
737a7a2
Compare
/ok-to-test |
/lgtm |
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.
Thanks so much @seanson!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrisz100, mikesplain, seanson 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 |
This is a proposed fix/improvement for issue #5700.
The current actual kops behavior is to tag shared subnets, but the documentation refers to having to manage your own tags. I feel it is best to keep the current subnet tagging behavior and add a toggle to disable. This will keep user experience standard by creating working clusters when using existing subnets but also allows power users to manually manage tags if they wish. Manual management of tags allows things like using separate dedicated subnets for internal ingress.