Grafana Operator is a Go-based, Apache-2.0 licensed Kubernetes operator that installs and manages Grafana instances, dashboards and data sources through Kubernetes and OpenShift custom resources, built for platform and observability teams that already run those clusters and want Grafana managed as code.

What it is

Grafana Operator lives in the Kubernetes and OpenShift ecosystem as a custom resource operator. It watches custom resources whose apiVersion is grafana.integreatly.org/v1beta1, including kind: Grafana and kind: GrafanaDashboard, and reconciles the actual Grafana deployment and its contents to match what those resources declare. It is written in Go and the registry record gives the license as Apache-2.0, with 1,387 stars, 471 forks and 54 open issues at the time of listing. Its documented home is https://grafana.github.io/grafana-operator/docs/, and the project is developed in the open under the grafana GitHub organisation, with a weekly public meeting on Mondays at 13:30 Central European time and questions handled through GitHub Issues.

The concrete problem it solves is the gap between a Grafana instance and the resources inside it. The README frames the switch as moving away from "traditional deployments": instead of provisioning Grafana separately and then hand-importing dashboard JSON, clicking data sources into place and configuring plugins per instance, an operator keeps both the instance and its contents declarative. The README states the same resource also manages Grafana instances "in and outside of Kubernetes", which means a team can point the operator at an external Grafana rather than only a cluster-hosted one. Because everything is expressed as custom resources, the same definitions can flow through Git and be applied by a pipeline rather than by a person.

Key capabilities

• Deploys and reconciles Grafana through kind: Grafana custom resources under apiVersion: grafana.integreatly.org/v1beta1, including inline configuration such as security.admin_user and security.admin_password.
• Manages dashboards as kind: GrafanaDashboard resources, with the dashboard payload supplied directly as JSON in the spec.json field and re-synchronised on a resyncPeriod such as 30s.
• Binds dashboards to instances with instanceSelector.matchLabels, so a GrafanaDashboard targets whichever Grafana resources carry the matching label.
• Installs through Helm with helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.25.0, or through Kustomize, OpenShift OLM, or plain Kubernetes, per the installation guide.
• Supports multi-instance and multi-namespace Grafana deployments, and manages external Grafana instances for GitOps integration.
• Fits GitOps workflows driven by ArgoCD and Flux CD, which the README names as the tools teams use to apply these resources.
• Ships with multi-architecture support and one-click installation through Operatorhub/OLM, and adapts its behaviour to Kubernetes versus OpenShift.

Who uses it and how

• Platform teams running GitOps pipelines, where Grafana dashboards and data sources are committed as YAML and applied by ArgoCD or Flux CD rather than edited in the Grafana UI.
• Organisations operating more than one Grafana instance, since the operator handles multi-instance and multi-namespace deployments "effortlessly" in the README's phrasing.
• OpenShift v4 administrators, who can install it through Operatorhub/OLM in one click rather than managing the operator by hand.
• Teams keeping Grafana outside the cluster, because the operator is documented as managing instances both inside and outside Kubernetes.
• Anyone standardising on infrastructure as code, for whom dashboards, data sources and plugins are code rather than console state.

Getting started

The README's first install option is the Helm chart: helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.25.0. Teams that prefer Kustomize, OpenShift OLM or direct Kubernetes manifests are pointed to the installation guide and the documentation under docs/.

How it compares

This listing provides no list of paid products that Grafana Operator replaces, and the facts name no directly equivalent operator in this registry, so it stands alone here. The tools it names alongside itself, ArgoCD and Flux CD, are GitOps delivery mechanisms that apply the operator's custom resources rather than substitutes for the operator itself.

When to use it — and when not to

A self-hoster must run a Kubernetes or OpenShift cluster, install and upgrade the operator and its CRDs, and then write and maintain the Grafana and GrafanaDashboard resources themselves; the facts give no hosted option, so the cluster is a hard prerequisite. Anyone without a cluster, or without a Git-based workflow for YAML, gets little from the operator and should configure Grafana directly. The trade-offs to weigh honestly: the record shows 54 open issues, the registry excerpt of the README is truncated and defers detail to external documentation, and dashboard content still has to be authored as JSON inside the resource even though the delivery path is declarative.

helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.25.0

apiVersion: grafana.integreatly.org/v1beta1
kind: Grafana
metadata:
  name: grafana
  labels:
    dashboards: "grafana"
spec:
  config:
    log:
      mode: "console"
    security:
      admin_user: root
      admin_password: secret

---
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDashboard
metadata:
  name: sample-dashboard
spec:
  resyncPeriod: 30s
  instanceSelector:
    matchLabels:
      dashboards: "grafana"
  json: >
    {
      "title": "Simple Dashboard",
      "timezone": "browser",
      "refresh": "5s",
      "panels": [],
      "time": {
        "from": "now-6h",
        "to": "now"
      }
    }