Disable default Dashboards in the Prometheus Community Helm Chart

1
votes

I deployed the kube-prometheus-stack helm chart. While this chart offers a really nice starting point it has lots of default dashboards which I do not want to use. In the values.yaml of the chart, there is an option defaultDashboardsEnabled: true, which seems to be what I am looking for but if I set it to false using the code below in my values file, which I mount into the helm chart, the dashboards are still there. Does anyone know why this does not work?

A possibility which I thought of is that the chart has both a subchart called grafana and an option grafana, but I do not know how I could fix it or test if this is the issue.

grafana: 
  defaultDashboardsEnabled: false
2
kubernetesprometheusgrafanakubernetes-helm
Have you tried to pull the repo (helm pull) locally and just remove the grafana directory from the template? – acid_fuji
Yes, that should work but I would rather stick to this Grafana version and understand how to modify the helm chart. – Manuel
How about setting grafana.enable: to false in values.yml? Just tested this and it does not install grafana with this flag. – acid_fuji

2 Answers

2
votes

I`m placing this answer to better visibility as community might interested in other solutions.

  • First way would be setting grafana.enable: to false in values.yaml.
## Using default values from https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
grafana:
  enabled: true

With this your chart will not install grafana.

  • Another way would be to helm pull the chart to your local directory and then just delete the template.grafana directory (to launch the chart locally you just need to helm install <name> ./prometheus-stack)
1
votes

I solved the issue by removing the namespace where Grafana was located. Apparently, there has been some resource left which was not removed by uninstalling the helm chart.

Edit: The problem seems to be with the configmaps. It appears that in some of these the old configuration is saved even though it has already been changed in the helm chart. Removing the Grafana deployment and all the config maps in the regarding namespace worked for me. Surely it is not necessary to remove all configmaps but I did not have the time to find out which one is the problem.