Skip to content
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

Merged
merged 7 commits into from
Apr 22, 2024

Conversation

ChrisVanLawAtFanatics
Copy link
Contributor

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 labels
  • console.additionalLabels added to values for console-specific labels

Copy link
Contributor

@ramondeklein ramondeklein left a 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.

@ramondeklein
Copy link
Contributor

@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).

helm/operator/templates/_helpers.tpl Show resolved Hide resolved
helm/operator/templates/_helpers.tpl Show resolved Hide resolved
helm/operator/templates/_helpers.tpl Show resolved Hide resolved
helm/tenant/templates/_helpers.tpl Show resolved Hide resolved
@ramondeklein
Copy link
Contributor

ramondeklein commented Apr 16, 2024

@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...

@ChrisVanLawAtFanatics
Copy link
Contributor Author

Thanks @ramondeklein! I appreciate your help on this and taking a look at the PR so quickly!

@cniackz cniackz self-assigned this Apr 20, 2024
@cniackz
Copy link
Contributor

cniackz commented Apr 20, 2024

@ramondeklein and @pjuarezd do you think we can merge it? or more changes are required?

@ramondeklein ramondeklein merged commit 01c56a5 into minio:master Apr 22, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants