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

Possibility to add additional labels on all helm chart resources #3437

Closed
bastienbosser opened this issue Oct 14, 2022 · 0 comments · Fixed by #3438
Closed

Possibility to add additional labels on all helm chart resources #3437

bastienbosser opened this issue Oct 14, 2022 · 0 comments · Fixed by #3438
Labels
component/deployment Helm chart, kubernetes templates and configuration Issues/PRs

Comments

@bastienbosser
Copy link

What new functionality do you want?

Add a commonLabels variable in the values.yml file that allows to add additional labels on all helm chart resources.

How would the end user gain value from having this feature?

As you know, labels can be used to organize and to select subsets of objects. In my case of use it allows me to group the applications by category and to check by a simple command the status of it.

As examples, for all security applications, I put a label "my-cluster-name/application_group: security". Then I just have to make the command "kubectl get all -A -l my-cluster-name/application_group=security" to know the status of all applications that provide security.

Add a list of criteria that should be met for this feature to be useful

I don't really know what you expect in this field

Additional context

Nothing to report

@nixpanic nixpanic added the component/deployment Helm chart, kubernetes templates and configuration Issues/PRs label Oct 19, 2022
@mergify mergify bot closed this as completed in #3438 Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/deployment Helm chart, kubernetes templates and configuration Issues/PRs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants