Should Grafana Operator be extended to other GrafanaLabs OSS ? #1849
Replies: 1 comment 1 reply
-
This topic has been discussed before on different occasions. We had meetings with the team of the loki operator, the tempo operator and the as-code team of Grafana Labs and decided to keep the operator focused on Grafana resources. Keeping the operators focused on specific projects allows for much better maintainability and is the recommended approach when designing operators. Each additional connection point introduces more edge cases and combinations to take care of, which is not possible with our small maintainer team. You can also check out the grafana/crossplane-provider project, which supports more resources (especially OnCall) than the Grafana operator doesn't. IMHO it's a bit harder to use but if it works for you, it is definitely a viable solution. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
There are many OSS at GrafanaLabs. The operator is awesome to manage dashboards and related resources.
I can't find operators for other products such as OnCall, Loki, Mimir or Tempo. I believe that it could be useful to fully automate the Grafana stack deployment (through GitOps per example) through a single operator installation.
I'm willing to contribute to such an extension. However, I'm not to decide if it should be in the roadmap or not.
What do you think?
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions