-
Notifications
You must be signed in to change notification settings - Fork 92
Persist grafana dashboards and make them editable #98
Comments
One potential solution that just occurred to me is to continue using the provisioning feature to provide the out-of-the-box dashboards, but then document or change the grafana deployment to use a PV/PVC for the grafana data location. There might be better solutions here though, but I am not super familiar with Grafana internals. |
Should be able to mount the dashboards to the PVC, then use an initContainer to drop in the template files and boostrap. |
Hi, I had used PV/PVC to store grafana data. But the dashboard and datasource will lost when restart the POD. volumeMounts: ubuntu@ip-10-0-2-43:~$ k get pv ubuntu@ip-10-0-2-43:~$ k get pvc -n monitoring |
Currently, grafana dashboards are deployed via the dashboard provisioning feature . This is great because the dashboards come pre-loaded with the grafana deployment. The downside, however, is that grafana does not support modifying these dashboards, and persisting the changes (we are also using configmaps, which are read-only).
Ideally, the grafana dashboards can be modified, and the changes persisted to something like a PV+PVC.
The text was updated successfully, but these errors were encountered: