grafana/grafana-operator v5.21.4

on GitHub

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

• @abh made their first contribution in #2413

Full Changelog: v5.21.3...v5.21.4