You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, despite not bringing huge advantages comparing to using the standalone application, I found that being able to provision new dashboards or datasources through the CRDs is indeed good, otherwise you would have to create ConfigMaps and add them as volumes attaching to the /provisioning directory on Grafana manually - if you want to provision datasources/dashboards on Grafana's startup that is.
It is especially useful if you are doing multiple deployments, for the reasons above.
@garethahealy@seravat yes, that is the specific use case we have here, as currently we are standing up a generic grafana deployment, and then individually "mounting" a dashboard as a CM to grafana, which requires a patch of the deployment to add the volume. This is not ideal, as this approach isn't very declarative, so we would like to replace it with the operator & dashboard CRD.
https://github.com/integr8ly/grafana-operator
The text was updated successfully, but these errors were encountered: