Comparison to Grafana Operator?
joebowbeer opened this issue · 4 comments
I like what I read about this project in a recent article.
As I dig in deeper, I realize that Grafana Operator also has CRDs for GrafanaDashboard, GrafanaDatasource, etc.
It would be useful to me if you added a comparison between the CRDs in this project and those in Grafana Operator.
Hey!
Glad to hear that :)
Mind sharing a link to that article? I'm curious.
Grafana Operator and DARK have very different scopes in term of the resources they can manage.
While DARK only manages dashboards, datasources, API keys, and the alertmanager, Grafana Operator can also manage and operate Grafana itself.
When if comes to dashboards and datasources, the main difference is in the choice of representation. Grafana Operator favors JSON (or jsonnet), DARK has its own YAML way of representing dashboards (based on grabana). Using YAML feels "more right" in a Kubernetes ecosystem, and having this abstraction layer also allows for less verbose and more succinct manifests.
A related question: How difficult would it be for Grafonnet to output DaRK resources?
I've never really used Grafonnet, so I can't answer for sure. But having done a JSON to DARK converter, I imagine that it would be tedious