Open kinikiti opened 5 months ago
So, I manage to find the problem.
If you enable HTTPS on Grafana URL http://localhost:3000
is not longer valid.
You can change URL to httpS://localhost:3000
. But if you are using not globally trusted certificate for Grafana (self-signed certificate, for example), sidecar container cannot make reload request because of the certificate issue.
You can mount volume with trust bundle (for example, generated by Trust Manager) to the pod, but there is not way to name file correctly for Alpine Linux.
We need something like subPath
for extraMounts
.
Conversion of the sidecars for the init containers works for Alarms and Datasources, but not possible for Dashboards.
I'm using latest Helm chart for Grafana installation on Kubernetes.
I'm using sidecars for alerts, dashboards and datasource provisioning. Data source comes from the secret and appears as a yaml file in Grafana container under
/etc/grafana/provisioning/datasources
File itself:grafana.ini
:I see that within container start Grafana provisioning alerts:
But I don't see any errors with Data Source provisioning. If I shell into container and start
grafana server
there it detectsdatasources.yaml
and provisions it without any single error or warning.What do I miss here? How can I provision Data Sources from secrets with Helm chart?
I see that dashboard provisioning works differently and they are stored as jsons under
/tmp/dashboards/*.json
. May this be related?