-
hi guys, there is an issue with the Grafana Operator in your projects.registry.vmware.com container registry, the latest build as per the below URL kicks out an error that the manifest is unknown. I'v…
-
### Name and Version
bitnami/grafana-operator 4.6.3
### What architecture are you using?
None
### What steps will reproduce the bug?
1. Use the Grafana Operator chart version 4.6.3 with the defau…
-
**Describe the bug**
When multiple Grafana instances exist in the same cluster and a GrafanaNotificationPolicy is created, the operator attempts to apply it to all Grafana instances
**Version**
5.14…
-
**Describe the issue**
Manual investigation of this Operator revealed that while the current installation still functions (v4), it is no longer a version maintained actively and thus should be migrate…
-
### Name and Version
bitnami/grafana-operator-4.7.4
### What architecture are you using?
None
### What steps will reproduce the bug?
1- Deploy Grafana with Grafana Operator version 5.14…
-
**Describe the bug**
Tried to install app grafana-operator from helm chart and ArgoCD fails to load target state.
```
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name:…
-
### What's wrong?
I'm trying to run Grafana Alloy for 3-rd party service. Replacing existing Grafana Agent with it. Grafana Agent scrapes target fine but Alloy altough discovering the ServiceMonitor …
-
**Is your feature request related to a problem? Please describe.**
If I have grafana labs deployments in multiple namespaces I also need to deploy the rollout-operator multiple times. This is ineffic…
-
### What happened?
``When creating datasources in Grafana via Kubernetes resources, each datasource appears correctly in the Grafana UI. However, accessing any newly created datasource shows the foll…
-
**Is your feature request related to a problem? Please describe.**
On our self-hosted Grafana Enterprise instance, we use **Organisations** to isolate our clients dashboards and **Teams** to structur…