[Bug] Cannot Create Dashboards in Other Namespaces than the Grafana-operator Namespace (EKS /k8s / helm) #1714
-
Describe the bug Version To Reproduce
Expected behavior Suspect component/Location where the bug might be occurring Config + Logs External Grafana Config
Dashboard Config
Logs from Operator:
Runtime (please complete the following information):
Additional context |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
For cross namespace imports, you need to enable them on the Grafana resource: |
Beta Was this translation helpful? Give feedback.
-
Thanks now it works ^^ |
Beta Was this translation helpful? Give feedback.
-
It is a pity that this cannot be set globally 😞. Imagine that you have one Grafana and many teams contributing with their objects (folders, dashboards, etc.), and each resource needs to have this $ kubectl get grafanadashboards.grafana.integreatly.org -A
NAMESPACE NAME NO MATCHING INSTANCES LAST RESYNC AGE
cosdashboards poc-sample2 52s 135m So, there are situations when teams complain that they don't see their newly added dashboards in Grafana even though there are no visible errors or info on why 🫤. |
Beta Was this translation helpful? Give feedback.
@NerdySoftPaw
allowCrossNamespaceImport: true
should be added to the individual manifests that are imported, specificallyGrafanaDashboards
,GrafanaContactPoints
, etc.I do not think it has any functional use on
Grafana
instances themselves.See: https://grafana.github.io/grafana-operator/docs/examples/crossnamespace/readme/