Skip to content

Use labels suggested by K8s and Helm best practices #173

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pinkavaj
Copy link

@pinkavaj pinkavaj commented Jun 14, 2025

This improves the compatibility and makes it easier to work with various tools, which take advantage from the assumption of existence of those labels.

https://helm.sh/docs/chart_best_practices/labels/
https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/

Changing the selectors is breaking change, so the bump of the major version of the helm chart.

@pinkavaj pinkavaj marked this pull request as ready for review June 15, 2025 06:18
@Mercbot7
Copy link
Contributor

Mercbot7 commented Jul 9, 2025

I like what this does but do have to ask. Why does it need to be a breaking change? can the labels not co-exist for a time and a deprecation notice be given?

@pinkavaj
Copy link
Author

pinkavaj commented Jul 9, 2025

I like what this does but do have to ask. Why does it need to be a breaking change? can the labels not co-exist for a time and a deprecation notice be given?

Sure they can, NP here. updated

Many tools can benefit from using those labels, providing either extra information
or simplifying life of many by unifying the labels zoo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants