-
Notifications
You must be signed in to change notification settings - Fork 401
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
DataSource needs to be managed through grafana API #655
Comments
@guimou can you please try version 4.1.0 (4.1.1) will be released soon instead. |
If it works with dashboard but not with datasource it's probably thanks to that we are using a configmap to insert the datasource. As mentioned in: #652 |
This issue hasn't been updated for a while, marking as stale, please respond within the next 7 days to remove this label |
@guimou we expect to fix this when switching to the API for data sources. |
OK, no worries. Do you want to leave this open til then, or do we close it? |
We will keep it open, it's a good way to track it. |
Resolved in #919 |
Hi!
When creating a DataSource through OpenShift Advanced Cluster Management, ACM, the datasource does not work. Other components (dashboard, Grafana instance works well).
The exact same deployment through an oc apply -k (like what ACM is doing) works perfectly.
We were able to pinpoint the problem. ACM is adding this in the GrafanaDataSource CR metadata:
When the ownerReferences section is removed manually, the operator picks up the DataSource and refreshes the deployment.
Version
3.10.3
To Reproduce
Create a datasource with the standard YAML config, and apply it through an ACM deployment.
Expected behavior
Datasource is picked up by the operator regarless of owner information.
Runtime (please complete the following information):
The text was updated successfully, but these errors were encountered: