Skip to content

fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.24.0 - autoclosed#1478

Closed
renovate-sh-app[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-grafana-grafana-operator-v5-5.x
Closed

fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.24.0 - autoclosed#1478
renovate-sh-app[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-grafana-grafana-operator-v5-5.x

Conversation

@renovate-sh-app

@renovate-sh-app renovate-sh-app Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

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

v5.24.0

Compare Source

Welcome to release 5.24.0 of the Grafana Operator!

This release contains an important security fix, and we urge you to update to this version as soon as possible. We are not aware of any breaking changes all through versions >= 5 so updates should be trivial.

Regarding features, this release includes support for fetching dashboards & library panels using OCI artifacts.

Upgrade instructions

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

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

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

New Contributors

Full Changelog: grafana/grafana-operator@v5.23.0...v5.24.0

v5.23.0

Compare Source

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

This release contains fixes for a bunch of long standing issues as well as quality-of-live improvements. It also bumps the default Grafana version to 13.0.1. Note that existing instances will not be updated automatically. To update them, modify the value of .spec.version.

Upgrade instructions

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

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

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

New Contributors

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

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 alig

Note

PR body was truncated to here.


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

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.com-grafana-grafana-operator-v5-5.x branch from c17e272 to 471e70c Compare May 27, 2026 23:09
@renovate-sh-app

renovate-sh-app Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ 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):

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

Details:

Package Change
go 1.25.9 -> 1.26.3
go.uber.org/zap v1.27.0 -> v1.28.0
k8s.io/api v0.34.3 -> v0.36.1
k8s.io/apiextensions-apiserver v0.34.3 -> v0.36.1
k8s.io/apimachinery v0.34.3 -> v0.36.1
k8s.io/apiserver v0.34.3 -> v0.36.1
k8s.io/client-go v0.34.3 -> v0.36.1
k8s.io/component-base v0.34.3 -> v0.36.1
k8s.io/klog/v2 v2.130.1 -> v2.140.0
sigs.k8s.io/controller-runtime v0.22.5 -> v0.24.1
github.com/emicklei/go-restful/v3 v3.12.2 -> v3.13.0
github.com/go-openapi/analysis v0.23.0 -> v0.25.2
github.com/go-openapi/errors v0.22.1 -> v0.22.7
github.com/go-openapi/jsonpointer v0.21.0 -> v0.23.1
github.com/go-openapi/jsonreference v0.21.0 -> v0.21.6
github.com/go-openapi/loads v0.22.0 -> v0.23.3
github.com/go-openapi/spec v0.21.0 -> v0.22.5
github.com/go-openapi/strfmt v0.23.0 -> v0.26.3
github.com/go-openapi/swag v0.23.1 -> v0.26.0
github.com/google/gnostic-models v0.7.0 -> v0.7.1
github.com/grafana/grafana-openapi-client-go v0.0.0-20250617151817-c0f8cbb88d5c -> v0.0.0-20260430175825-547a3b5a00a5
github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.3 -> v2.27.7
github.com/sirupsen/logrus v1.9.3 -> v1.9.4
github.com/stretchr/objx v0.5.2 -> v0.5.3
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.58.0 -> v0.67.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 -> v1.40.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.34.0 -> v1.40.0
go.opentelemetry.io/proto/otlp v1.5.0 -> v1.9.0
golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 -> v0.0.0-20251219203646-944ab1f22d93
golang.org/x/oauth2 v0.34.0 -> v0.36.0
golang.org/x/time v0.9.0 -> v0.15.0
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v2.5.0
google.golang.org/genproto/googleapis/api v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260128011058-8636f8732409
google.golang.org/genproto/googleapis/rpc v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260128011058-8636f8732409
google.golang.org/protobuf v1.36.11 -> v1.36.12-0.20260120151049-f2248ac996af
k8s.io/kube-openapi v0.0.0-20250910181357-589584f1c912 -> v0.0.0-20260317180543-43fb72c5454a
sigs.k8s.io/structured-merge-diff/v6 v6.3.2-0.20260122202528-d9cc6641c482 -> v6.4.0

@renovate-sh-app renovate-sh-app Bot force-pushed the renovate/github.com-grafana-grafana-operator-v5-5.x branch from 471e70c to 62cbd95 Compare May 28, 2026 23:53
@renovate-sh-app renovate-sh-app Bot force-pushed the renovate/github.com-grafana-grafana-operator-v5-5.x branch from 62cbd95 to ab87597 Compare June 12, 2026 14:12
@renovate-sh-app renovate-sh-app Bot changed the title fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.23.0 fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.24.0 Jun 12, 2026
@renovate-sh-app renovate-sh-app Bot force-pushed the renovate/github.com-grafana-grafana-operator-v5-5.x branch from ab87597 to 03e1c44 Compare June 15, 2026 17:12
….24.0

| datasource | package                                | from    | to      |
| ---------- | -------------------------------------- | ------- | ------- |
| go         | github.com/grafana/grafana-operator/v5 | v5.19.4 | v5.24.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.com-grafana-grafana-operator-v5-5.x branch from 03e1c44 to c6ec624 Compare June 16, 2026 11:12
@renovate-sh-app renovate-sh-app Bot changed the title fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.24.0 fix(deps): update module github.com/grafana/grafana-operator/v5 to v5.24.0 - autoclosed Jun 20, 2026
@renovate-sh-app renovate-sh-app Bot closed this Jun 20, 2026
@renovate-sh-app renovate-sh-app Bot deleted the renovate/github.com-grafana-grafana-operator-v5-5.x branch June 20, 2026 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants