Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore standing up grafana via the Grafana operator #26

Closed
etsauer opened this issue Nov 20, 2019 · 4 comments
Closed

Explore standing up grafana via the Grafana operator #26

etsauer opened this issue Nov 20, 2019 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@etsauer
Copy link
Collaborator

etsauer commented Nov 20, 2019

https://github.com/integr8ly/grafana-operator

@garethahealy
Copy link
Contributor

garethahealy commented Nov 20, 2019

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

@seravat
Copy link

seravat commented Nov 21, 2019

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
Copy link
Collaborator Author

etsauer commented Nov 21, 2019

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

@etsauer etsauer added this to the v1.2 milestone Nov 27, 2019
@etsauer etsauer added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 27, 2019
@ramius345 ramius345 self-assigned this Dec 3, 2019
@ramius345
Copy link
Contributor

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

@etsauer etsauer self-assigned this Apr 3, 2020
@etsauer etsauer closed this as completed Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants