-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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 elb tagging #6703
Fix elb tagging #6703
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikesplain 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 |
4d3a48d
to
7b9166f
Compare
This comment has been minimized.
This comment has been minimized.
1b72b4b
to
d6c02d3
Compare
/assign @chrisz100 |
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
Loving the test coverage. Something we should work on some time too...
…03-origin-release-1.12 Automated cherry pick of #6703: Fix tagging and remove tagging elbs
Quick question on the tags. The tagging standards on ELB seem to be more restricted than other services limiting keys/values to be complaint of the pattern "^([\p{L}\p{Z}\p{N}_.:/=+-@]*)$" Would it be a good idea to validate/handle them here? |
Turns out we weren't tagging quite right, also needed to add a removal function.
To note, this also adds a new tag to existing elbs since we're now using
b.Cluster.Spec.CloudLabels
to generate the elb tags:I don't believe this should have any negative effects.
Fixes: #6646, #2048
Since this was included in 1.12 and has some weird effects, I think we should cherry-pick it in.