-
Notifications
You must be signed in to change notification settings - Fork 537
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
Add possibility do add common labels in helm chart #9067
Comments
This is necessary for having common alerts and route them based on label(s).
|
Signed-off-by: fabio trigari <[email protected]>
I created a PR. All objects created by Helm now have the It's important to keep the same values from the other projects mentioned, so lgtm chart could apply them to all its subchart. Regarding Mimir's dependencies, how would you like to proceed? Should I open separate issue for rollout-operator and grafana-object-operator and link them to this one? For MinIO chart the only solution is to open an issue and develop it. Do you have any better ideas? Update I created PRs for |
…na#9067) Signed-off-by: fabio trigari <[email protected]>
… bucket job (grafana#9067) Signed-off-by: fabio trigari <[email protected]>
Is your feature request related to a problem? Please describe.
A lot of Helm charts (e.g. kube-prometheus-stack, cert-manager) allow to define key
commonLabels
, which results in a set of custom labels added to every resource created by the chart (pods, deployments, statefulsets, ingresses, services, servicemonitors, crds, etc.). Right now it is not even possible to add custom labels to Mimir's deployments or statefulsets (other than by using kustomize).Use case: e.g. we want to have generic alerts (like: pod is crashlooping) that are dynamically routed, based on the label
team
(on the same cluster there is stuff deployed by various teams)Describe the solution you'd like
In
values.yaml
we should be able to specify something like this:and all resources created by Mimir chart will have those labels
The text was updated successfully, but these errors were encountered: