grafana/grizzly

Kubernetes Operator

sathieu opened this issue · 4 comments

sathieu commented

Could grizzly be run as a Kubernetes Operator with custom resources definitions for Orgs, Datasources, Dashboard, ... ?

malcolmholmes commented

This is not something that it has been designed for at this point. Can you not use the existing Grafana Operator?

malcolmholmes commented

In terms of automation, Grizzly is more likely to run in a CI job and push resources from there.

sathieu commented

@malcolmholmes OK. This is hard to find a complete solution for my usecase, all of the evaluated solutions have missing features :

  • Grafana provisioning is not able to use OrgName for datasources and dashboard (I created grafana#76937 which is blocked by an unscheduled UID migration)
  • Grafana provisioning is not able to create Orgs (I created grafana/grafana#78253, which was closed, pointing to grizzly)
  • Grizzly has no Org management (#268)
  • Grizzly has no support for OrgName is datasources and dashboard (I just created #278)
  • Grafana Operator has no Org support (see here)
  • ...
malcolmholmes commented

There is already a Kubernetes operator for Grafana, so doesn't make sense to make Grafana operate in this way. Would make more sense to add support to respective tools than convert an existing tool.

Also, note that orgs is a feature in Grafana that is unlikely to see much development - more likely to see it removed some time in the future.