Explore standing up grafana via the Grafana operator about pelorus

[garethahealy]

@seravat ; since you've used this @customer recently. Can you give a quick summary of it? anything learned, etc

[seravat]

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.

[etsauer]

@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.

[ramius345]

I think I got this working, here is a PR for you to look at.
#37