Skip to content

chore(deps): update dependency grafana/grafana-operator to v5.22.2#1819

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/grafana-grafana-operator-5.x
Open

chore(deps): update dependency grafana/grafana-operator to v5.22.2#1819
renovate[bot] wants to merge 1 commit intomainfrom
renovate/grafana-grafana-operator-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 6, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
grafana/grafana-operator minor v5.18.0 → v5.22.2

Release Notes

grafana/grafana-operator (grafana/grafana-operator)

v5.22.2

Compare Source

This release fixes issues around CEL validation rules and kubernetes compatibility. No changes were made to the functionality of the operator since the last release.

When updating, you should ideally update to this release directly, skipping 5.22.0 and 5.22.1 to prevent issues during CRD updates.

What's Changed

Fixes
  • fix(api): escape reserved identifiers in CEL rules to improve compatibility with k8s < 1.32 by @​weisdd in #​2583
  • fix(api): incomplete CEL for namespace immutability check in GrafanaManifest by @​weisdd in #​2584
Dependencies
Documentation

Full Changelog: grafana/grafana-operator@v5.22.1...v5.22.2

v5.22.1

Compare Source

Changes worth paying attention to

  • new emptyDir volume with /tmp mount point and deprecation of TMPDIR env:
    • starting from Grafana v12.4.0, plugins no longer have access to all environment variables by default (PR). It means that TMPDIR env, which we have previously used to override temporary location for plugin downloads, is now ignored. To mitigate that change on the operator side, we backed /tmp by an emptyDir volume and stopped adding TMPDIR env (the alternative was to generate forward_host_env_vars setting in plugins section of a configMap, which would be overly complex for our needs). It works with any Grafana version, so should be a transparent change for most users. In case you, for some reasons, have some manual volume overrides for /tmp as well, it would be a good idea to remove those;
  • deprecation of pre-provisioned receivers:
    • starting from Grafana v12.4.0, the pre-provisioned set of receivers has changed (PR), so, if you happen to rely on one of those (e.g. default-receiver, grafana-default-email), before upgrading to v12.4.0+, you should migrate to a custom receiver (use GrafanaContactPoint CR to provision one). It's also an option to rely on empty receiver instead, but it's available only in v12.4.0+, so you'd have to upgrade all matching Grafana instances at once;
  • RBAC for events:
    • with v5.22.0, you might have noticed in logs that the operator fails to generate LeaderElection events. It appears that controller-runtime still depends on core API ("") to generate this specific event. All the other events get recorded using events.k8s.io API group. Our RBAC manifests have been extended to accomodate both groups (thanks to @​tamcore).

What's Changed

Breaking changes
Fixes
Dependencies
Documentation
Other Changes

Full Changelog: grafana/grafana-operator@v5.22.0...v5.22.1

v5.22.0

Compare Source

We're happy to announce version 5.22.0 of the Grafana Operator!

This release contains a bunch of new and exciting features like:

  • The brand new GrafanaManifest resource
    • This allows you to manage resources previously not supported by the operator but available through the new Kuberentes-style Grafana APIs (e.g Playlists, ShortURLs) as well as resources introduced by plugins (e.g. Frontend O11y configuration in Grafana Cloud).
  • Dynamic resource patching (currently only available to GrafanaManifest resources)
    • Patch resources with arbitrary jq scripts before submitting them to the Grafana API!
  • Alert rule groups have been updated to support more fields exposed by the Grafana API
  • Service accounts no longer require a name and will default to metadata.name

Upgrade instructions

Using Helm
# Upgrade the operator image & deployment
helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.22.0

# Upgrading CRDs
kubectl apply --server-side --force-conflicts -f https://github.com/grafana/grafana-operator/releases/download/v5.22.0/crds.yaml
Using kubectl
# Namespace Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.22.0/kustomize-namespace_scoped.yaml

# Cluster Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.22.0/kustomize-cluster_scoped.yaml
Using kustomize
flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.22.0 --output ./grafana-operator/
Using OLM

Releases are published to operatorhub.io as well as the OpenShift Operator Catalog. Depending on the installation, existing installations will either upgrade automatically or require approval from an administrator.

What's Changed

Changes that might need your attention
  • chore(Helm): simplify helm chart by @​Baarsgaard in #​2463
    • We changed the default fallback for the cache strategy to safe instead of off. If you haven't explicitly set enforceCacheLabels to null, this does not affect you.
Features
Fixes
  • fix(GrafanaDashboard): update Grafana status even when remote state matches by @​weisdd in #​2440
  • fix(AlertRuleGroup): skip reconciliation when there's no drift in remote state by @​heliapb in #​2439
  • fix(GrafanaAlertRuleGroup): allow deprecated fields dashboardUid and panelId by @​Baarsgaard in #​2450
  • fix(logs): Leader election log format by @​Baarsgaard in #​2466
  • fix: add CRD validation for URLs in external grafana, dashboards, and library panels by @​heliapb in #​2446
  • fix(GrafanaManifest): consider forbidden error as success when deleting manifests by @​theSuess in #​2468
  • fix(helm): missing list namespaces permission with watchNamespaceSelector by @​Baarsgaard in #​2465
  • fix(Grafana): missing HTTPRoute backendRefs (alternative solution) by @​weisdd in #​2510
  • fix(GrafanaContactPoint): use list based matching as a workaround for 10.4.0-10.4.5 by @​theSuess in #​2507
Dependencies
Documentation
Other Changes

New Contributors

Full Changelog: grafana/grafana-operator@v5.21.4...v5.22.0

v5.21.4

Compare Source

This release contains a few fixes around HTTPRoute CRD discovery, kustomize artifacts, and NotificationPolicy validations.

What's Changed

Breaking changes
  • fix(NotificationPolicy): disable invalid fields on .spec.route by @​Baarsgaard in #​2270:
    • even though, technically, the change is breaking, it may only affect configurations and k8s versions that we do not support:
      • essentially, we added CEL-rules prohibiting usage of a few top-level fields inside .spec.route. Those fields have never had any effect, so should have never been used by anyone in the first place. More details can be found in the related PR;
      • some of those rules rely on a CEL function that is not available on k8s <= 1.31.x. 1.31 has already reached its EOL, so it should not be an issue either;
    • if any of the changes mentioned above prevent you from upgrading, you may simply skip CRD upgrade this time (e.g. keep using the one from v5.21.3, it differs only around those validations).
Fixes
  • fix(autodetect): HTTPRoute discovery for partial Gateway API CRD set by @​weisdd in #​2417:
    • previously, the operator would assume that users would have either all Gateway API CRDs installed or none of them. As a consequence, if HTTPRoute CRD was actually missing, the operator would crash while trying to do cache fine-tuning (part of the start-up process). From now on, the operator will specifically check for HTTPRoute CRD instead;
  • fix(kustomize): remove stale image override from cluster_scoped overlay by @​abh in #​2413:
    • it appears that, starting from v5.18.0, cluster-scoped kustomize artifacts (kustomize-cluster_scoped.yaml) have contained a stale image override. Those artifacts, based on our pull stats, are not widely used, so the effect was minimal. In any case, we'll adjust our Makefile targets to prevent accidental image overrides.

New Contributors

Full Changelog: grafana/grafana-operator@v5.21.3...v5.21.4

v5.21.3

Compare Source

NOTE: This patch release is aimed to fix a bug in the helm chart around setting the default value for image.repository (in earlier v5.21.x versions, it should have been set to grafana/grafana-operator, not to ghcr.io/grafana/grafana-operator, which resulted in ErrImagePull errors).

What's Changed

Fixes

Full Changelog: grafana/grafana-operator@v5.21.2...v5.21.3

v5.21.2

Compare Source

NOTE: due to a bug in our workflow, image.repository in the helm chart is set to ghcr.io/grafana/grafana-operator (instead of grafana/grafana-operator), which will lead to the ErrImagePull error in Kubernetes. You can either do a manual override or wait for chart 5.21.3.

What's Changed

Fixes

Full Changelog: grafana/grafana-operator@v5.21.1...v5.21.2

v5.21.1

Compare Source

NOTE: functionality-wise, v5.21.1 is the same as v5.21.0. - The patch release contains only a fix for our helm publishing workflow. Make sure to use 5.21.1 tag for helm chart.

NOTE: due to a bug in our workflow, image.repository in the helm chart is set to ghcr.io/grafana/grafana-operator (instead of grafana/grafana-operator), which will lead to the ErrImagePull error in Kubernetes. You can either do a manual override or wait for chart 5.21.3.

Welcome to release 5.21.1 of the Grafana Operator!

It mainly includes bug fixes but also some cool new features (like kubernetes-native JWT authentication, HTTPRoute support or more flexible date parsing in alert rule groups).

We also made some changes to the helm chart. One minor change is that we removed the v prefix from our chart versions which should hopefully simplify OCI installations. We also aligned the image.repository value with other Grafana helm charts which might cause issues. More details can be found in the next section.

Breaking changes to the helm chart

If you've been using the image.repository field to change the image, this field has been split into registry and repository to align with the rest of the Grafana helm charts.

To migrate any custom values to this new format, follow this example:

Migration example

If your values.yaml contained this:

image:
  repository: example.com/my-custom/grafana-operator

you'll need to replace it with this:

image:
   registry: example.com
   repository: my-custom/grafana-operator
If you haven't changed this field in your values.yaml, you can safely ignore this.

Upgrade instructions

Using Helm
# Upgrade the operator image & deployment
helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.21.1

# Upgrading CRDs
kubectl apply --server-side --force-conflicts -f https://github.com/grafana/grafana-operator/releases/download/v5.21.1/crds.yaml
Using kubectl
# Namespace Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.21.1/kustomize-namespace_scoped.yaml

# Cluster Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.21.1/kustomize-cluster_scoped.yaml
Using kustomize
flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.21.1 --output ./grafana-operator/
Using OLM

Releases are published to operatorhub.io as well as the OpenShift Operator Catalog. Depending on the installation, existing installations will either upgrade automatically or require approval from an administrator.

What's Changed

Features
Fixes
Dependencies

New Contributors

Full Changelog: grafana/grafana-operator@v5.20.0...v5.21.0

v5.21.0

Compare Source

Welcome to release 5.21.0 of the Grafana Operator!

It mainly includes bug fixes but also some cool new features (like kubernetes-native JWT authentication, HTTPRoute support or more flexible date parsing in alert rule groups).

We also made some changes to the helm chart. One minor change is that we removed the v prefix from our chart versions which should hopefully simplify OCI installations. We also aligned the image.repository value with other Grafana helm charts which might cause issues. More details can be found in the next section.

Breaking changes to the helm chart

If you've been using the image.repository field to change the image, this field has been split into registry and repository to align with the rest of the Grafana helm charts.

To migrate any custom values to this new format, follow this example:

Migration example

If your values.yaml contained this:

image:
  repository: example.com/my-custom/grafana-operator

you'll need to replace it with this:

image:
   registry: example.com
   repository: my-custom/grafana-operator
If you haven't changed this field in your values.yaml, you can safely ignore this.

Upgrade instructions

Using Helm
# Upgrade the operator image & deployment
helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version 5.21.0

# Upgrading CRDs
kubectl apply --server-side --force-conflicts -f https://github.com/grafana/grafana-operator/releases/download/v5.21.0/crds.yaml
Using kubectl
# Namespace Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.21.0/kustomize-namespace_scoped.yaml

# Cluster Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.21.0/kustomize-cluster_scoped.yaml
Using kustomize
flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.21.0 --output ./grafana-operator/
Using OLM

Releases are published to operatorhub.io as well as the OpenShift Operator Catalog. Depending on the installation, existing installations will either upgrade automatically or require approval from an administrator.

What's Changed

Features
Fixes
Dependencies

New Contributors

Full Changelog: grafana/grafana-operator@v5.20.0...v5.21.0

v5.20.0

Compare Source

Welcome to release 5.20.0 of the Grafana Operator!

The biggest new feature is support for service account management using the operator. We also added some other quality of live improvements (like the ability to use latest as a plugin version) and implemented some long overdue bug fixes!

Upgrade instructions

Using Helm
# Upgrade the operator image & deployment
helm upgrade -i grafana-operator oci://ghcr.io/grafana/helm-charts/grafana-operator --version v5.20.0

# Upgrading CRDs
kubectl apply --server-side --force-conflicts -f https://github.com/grafana/grafana-operator/releases/download/v5.20.0/crds.yaml
Using kubectl
# Namespace Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.20.0/kustomize-namespace_scoped.yaml

# Cluster Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.20.0/kustomize-cluster_scoped.yaml
Using kustomize
flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.20.0 --output ./grafana-operator/
Using OLM

Releases are published to operatorhub.io as well as the OpenShift Operator Catalog. Depending on the installation, existing installations will either upgrade automatically or require approval from an administrator.

What's Changed

Features
Fixes
  • fix(plugins): properly handle version preference in Sanitize, add CRD plugin validations by @​weisdd in #​2162
  • fix(plugins): ConfigMap key collisions for cross-namespace ds/db/lp with the same names by @​weisdd in #​2170
  • fix(plugins): remove ConfigMap key if no plugins left by @​weisdd in #​2179
  • fix(librarypanel): finalize plugins, mitigate HTTP errors for non-existent panels by @​weisdd in #​2180
Dependencies

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Jan 6, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 6, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 11.56%. Comparing base (96d06c7) to head (1bfc855).

Additional details and impacted files 
@@            Coverage Diff             @@
##             main    #1819      +/-   ##
==========================================
- Coverage   11.58%   11.56%   -0.02%     
==========================================
  Files         248      248              
  Lines       11405    11405              
==========================================
- Hits         1321     1319       -2     
- Misses      10040    10041       +1     
- Partials       44       45       +1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch 2 times, most recently from 10219fd to 5c53a54 Compare January 8, 2026 12:29
@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from 5c53a54 to 7fc94f0 Compare February 2, 2026 17:00
Copilot AI review requested due to automatic review settings February 12, 2026 18:02
@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from 7fc94f0 to f412585 Compare February 12, 2026 18:02
Copilot AI reviewed Feb 12, 2026
View reviewed changes
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from f412585 to 5c9c8f5 Compare February 24, 2026 11:02
@renovate renovate Bot changed the title chore(deps): update dependency grafana/grafana-operator to v5.21.4 chore(deps): update dependency grafana/grafana-operator to v5.22.0 Feb 24, 2026
Copilot AI review requested due to automatic review settings March 13, 2026 21:01
@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from 5c9c8f5 to e460950 Compare March 13, 2026 21:01
@renovate renovate Bot changed the title chore(deps): update dependency grafana/grafana-operator to v5.22.0 chore(deps): update dependency grafana/grafana-operator to v5.22.1 Mar 13, 2026
@renovate renovate Bot review requested due to automatic review settings March 13, 2026 21:01
@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from e460950 to afc93f2 Compare March 17, 2026 13:50
Copilot AI review requested due to automatic review settings March 17, 2026 13:50
@renovate renovate Bot changed the title chore(deps): update dependency grafana/grafana-operator to v5.22.1 chore(deps): update dependency grafana/grafana-operator to v5.22.2 Mar 17, 2026
@renovate renovate Bot review requested due to automatic review settings March 17, 2026 13:50
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 17, 2026

This pull request has been marked as stale because it has been inactive for more than 30 days. Please update this pull request or it will be automatically closed in 30 days.

@github-actions github-actions Bot added the Stale label Apr 17, 2026
Copilot AI review requested due to automatic review settings April 19, 2026 06:49
@renovate renovate Bot force-pushed the renovate/grafana-grafana-operator-5.x branch from afc93f2 to 1bfc855 Compare April 19, 2026 06:49
@renovate renovate Bot review requested due to automatic review settings April 19, 2026 06:49
@github-actions github-actions Bot removed the Stale label Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant