Skip to content

fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.22.0#1387

Open
renovate-sh-app[bot] wants to merge 1 commit intomainfrom
renovate/github.amrom.workers.dev-grafana-grafana-operator-v5-5.x
Open

fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.22.0#1387
renovate-sh-app[bot] wants to merge 1 commit intomainfrom
renovate/github.amrom.workers.dev-grafana-grafana-operator-v5-5.x

Conversation

@renovate-sh-app
Copy link
Contributor

@renovate-sh-app renovate-sh-app bot commented Feb 16, 2026 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
github.com/grafana/grafana-operator/v5 v5.19.4 → v5.22.0 age confidence

Release Notes

grafana/grafana-operator (github.com/grafana/grafana-operator/v5)

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

New Contributors

Full Changelog: grafana/grafana-operator@v5.19.0...v5.20.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

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

@renovate-sh-app renovate-sh-app bot force-pushed the renovate/github.amrom.workers.dev-grafana-grafana-operator-v5-5.x branch from 15981fd to a679f40 Compare February 24, 2026 01:15
@renovate-sh-app
Copy link
Contributor Author

renovate-sh-app bot commented Feb 24, 2026 •
edited
Loading

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 31 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.24.2 -> 1.26.0
github.com/prometheus/common v0.67.4 -> v0.67.5
go.uber.org/zap v1.27.0 -> v1.27.1
k8s.io/api v0.34.3 -> v0.35.1
k8s.io/apiextensions-apiserver v0.34.3 -> v0.35.1
k8s.io/apimachinery v0.34.3 -> v0.35.1
k8s.io/apiserver v0.34.3 -> v0.35.1
k8s.io/client-go v0.34.3 -> v0.35.1
k8s.io/component-base v0.34.3 -> v0.35.1
sigs.k8s.io/controller-runtime v0.22.5 -> v0.23.1
github.com/emicklei/go-restful/v3 v3.12.2 -> v3.13.0
github.com/go-openapi/analysis v0.23.0 -> v0.24.1
github.com/go-openapi/errors v0.22.1 -> v0.22.4
github.com/go-openapi/jsonpointer v0.21.0 -> v0.22.4
github.com/go-openapi/jsonreference v0.21.0 -> v0.21.4
github.com/go-openapi/loads v0.22.0 -> v0.23.2
github.com/go-openapi/spec v0.21.0 -> v0.22.3
github.com/go-openapi/strfmt v0.23.0 -> v0.25.0
github.com/go-openapi/swag v0.23.1 -> v0.24.1
github.com/grafana/grafana-openapi-client-go v0.0.0-20250617151817-c0f8cbb88d5c -> v0.0.0-20251202103709-7ef691d4df1d
github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.3 -> v2.27.3
go.mongodb.org/mongo-driver v1.14.0 -> v1.17.6
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.58.0 -> v0.64.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 -> v1.39.0
go.opentelemetry.io/proto/otlp v1.5.0 -> v1.9.0
golang.org/x/oauth2 v0.32.0 -> v0.34.0
golang.org/x/time v0.9.0 -> v0.12.0
google.golang.org/genproto/googleapis/api v0.0.0-20250303144028-a0af3efb3deb -> v0.0.0-20251202230838-ff82c1b0f217
google.golang.org/genproto/googleapis/rpc v0.0.0-20250303144028-a0af3efb3deb -> v0.0.0-20251202230838-ff82c1b0f217
google.golang.org/grpc v1.72.1 -> v1.78.0
google.golang.org/protobuf v1.36.10 -> v1.36.11
k8s.io/kube-openapi v0.0.0-20250910181357-589584f1c912 -> v0.0.0-20251125145642-4e65d59e963e

@renovate-sh-app renovate-sh-app bot force-pushed the renovate/github.amrom.workers.dev-grafana-grafana-operator-v5-5.x branch from a679f40 to a32525f Compare February 27, 2026 11:13
@renovate-sh-app renovate-sh-app bot changed the title fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.21.4 fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.22.0 Feb 27, 2026
@renovate-sh-app
fix(deps): update module github.com/grafana/grafana-operator/v5 to v5…
dfc5f21 
….22.0

| datasource | package                                | from    | to      |
| ---------- | -------------------------------------- | ------- | ------- |
| go         | github.com/grafana/grafana-operator/v5 | v5.19.4 | v5.22.0 |


Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
@renovate-sh-app renovate-sh-app bot force-pushed the renovate/github.amrom.workers.dev-grafana-grafana-operator-v5-5.x branch from a32525f to dfc5f21 Compare March 3, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

update-minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants