[Bug] Unable to provision dashboards if the grafana instance is defined in a different namespace

[alita1991]

Describe the bug
I have a use case where I must allow each user to create new Grafana dashboards from different namespaces. While testing the grafana-operator, I noticed that I was not able to create new dashboards if they belonged to a different namespace than the one to which the Grafana CR belongs. Is important to mention that the Grafana CR is configured to point to an external instance, inside of the k8s cluster and the dashboard creation was tested with success in the current namespace of Grafana CR.

Version
v5.4.1

To Reproduce
Steps to reproduce the behavior:

1. Create a Grafana CR resource in a custom namespace (ex: integration)
2. Create a Grafana Dashboard in the same namespace as Grafana CR (ex: integration)
3. Dashboard should be created in Grafana (working)
4. Create a Grafana Dashboard CR in a different namespace (ex: default)
5. Dashboard should be created in Grafana (not working)

Expected behavior
Dashboards should be created, even if the Grafana CR is defined in a different namespace.

[maciekm]

have you tried setting: allowCrossNamespaceImport: true?
see https://github.com/grafana-operator/grafana-operator/tree/master/examples/crossnamespace

looks like its required on dashboards, data sources and folders: code

[alita1991]

Hi @maciekm,

I tested the flag, everything works as expected.

Thank you