-
Notifications
You must be signed in to change notification settings - Fork 459
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
allow arbitrary labels to be set on operator and console resources #2069
Conversation
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.
This PR also provides a bugfix, because it did apply operator labels to the console, so good to have this fixed. I can imagine why this could be useful, but I don't really like to add the selector labels (meant for the deployments) to all other objects too.
f8e6334
to
d97dd66
Compare
@ChrisVanLawAtFanatics I have made some changes (and cleaned up a little). I think your functionality is still supported, but it's a bit cleaner (IMHO). |
@cesnietor Do you know what could be causing the test-decommision job to fail? It looks like it properly created all resources and something fails during teardown. UPDATE: Second run went fine. Not sure what's going on... |
Thanks @ramondeklein! I appreciate your help on this and taking a look at the PR so quickly! |
@ramondeklein and @pjuarezd do you think we can merge it? or more changes are required? |
Allow arbitrary labels to be set for console and operator resources via values. This allows better management of created resources as well as integration with other tools e.g. by setting tags for datadog.
operator.additionalLabels
added to values for operator-specific labelsconsole.additionalLabels
added to values for console-specific labels