Use Kubernetes/Helm recommended labels
See original GitHub issueDescribe the feature:
Currently, in all charts/versions, the old Helm labels are used e.g. release
, chart
, and app
.
Helm has already moved from those labels since 2018, and a new set of labels has been introduced and recommended by Helm and Kubernetes.
Describe a specific use case for the feature:
Working with the resources that created by Elastic Helm charts is not unified and doesn’t follow the best practices in terms of labeling.
If you agree to the change, I will make the change for each chart one by one (we could also keep the old behavior for compatibility and to be deprecated later).
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Labels and Annotations - Helm
Helm itself never requires that a particular label be present. Labels that are marked REC are recommended, and should be placed onto a...
Read more >Recommended Labels | Kubernetes
Recommended Labels. You can visualize and manage Kubernetes objects with more tools than kubectl and the dashboard. A common set of labels ......
Read more >Helm Chart Labels and Selectors - Stack Overflow
Because of I am new to using Helm, I have some confusion to use selector and labels. So how should use the labels...
Read more >Using Labels - Helm Documentation - Read the Docs
In Kubernetes, labels are typically edited by hand and stored with manifests in a version control system. Helm Classic makes it easier to...
Read more >Setting Kubernetes Labels and Annotations - DZone Cloud
Helm chart is a popular method of packaging applications to be installed on the Kubernetes cluster. As Helm chart developers, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I guess we could but not sure when we would have some time for review tbh