Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2026

This PR contains the following updates:

Package Update Change
grafana/grafana-operator minor v5.18.0v5.21.4

Release Notes

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

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

New Contributors

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

v5.19.4

Compare Source

This minor release only contains changes to the release pipeline, no functionality has been added or removed
See the v5.19.0 release notes for more details.

v5.19.3

Compare Source

This minor release only contains changes to the release pipeline, no functionality has been added or removed
See the v5.19.0 release notes for more details.

v5.19.2

Compare Source

This minor release only contains changes to the release pipeline, no functionality has been added or removed
See the v5.19.0 release notes for more details.

v5.19.1

Compare Source

This minor release only contains changes to the release pipeline, no functionality has been added or removed
See the v5.19.0 release notes for more details.

v5.19.0

Compare Source

Welcome to release 5.19.0 of the Grafana Operator!

This release features many smaller enhancements, like better status updates for most resources, as well as updating our spec to match changes in dependencies (more fields in alert rule groups, improved ingress & route support etc.).

We're also improving our image signing process. This is the first release after this change so we might push out a new minor release soon if something is not quite working.

Upgrade instructions

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

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

# Cluster Scope
kubectl replace -f https://github.com/grafana/grafana-operator/releases/download/v5.19.0/kustomize-cluster_scoped.yaml 
Using kustomize
flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.19.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.18.0...v5.19.0


Configuration

📅 Schedule: 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

codecov bot commented Jan 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 7.64%. Comparing base (6516195) to head (5c53a54).

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1819   +/-   ##
=====================================
  Coverage   7.64%   7.64%           
=====================================
  Files        213     213           
  Lines       9151    9151           
=====================================
  Hits         700     700           
  Misses      8424    8424           
  Partials      27      27           

☔ 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 from f761ab0 to 10219fd Compare January 8, 2026 11:37
@renovate renovate bot force-pushed the renovate/grafana-grafana-operator-5.x branch from 10219fd to 5c53a54 Compare January 8, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant