chore(deps): update dependency grafana/grafana-operator to v5.21.4 #1819
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.18.0→v5.21.4Release Notes
grafana/grafana-operator (grafana/grafana-operator)
v5.21.4Compare Source
This release contains a few fixes around
HTTPRouteCRD discovery, kustomize artifacts, andNotificationPolicyvalidations.What's Changed
Breaking changes
.spec.routeby @Baarsgaard in #2270:.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;Fixes
HTTPRouteCRD 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 forHTTPRouteCRD instead;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.3Compare 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 tografana/grafana-operator, not toghcr.io/grafana/grafana-operator, which resulted inErrImagePullerrors).What's Changed
Fixes
Full Changelog: grafana/grafana-operator@v5.21.2...v5.21.3
v5.21.2Compare Source
NOTE: due to a bug in our workflow,
image.repositoryin the helm chart is set toghcr.io/grafana/grafana-operator(instead ofgrafana/grafana-operator), which will lead to theErrImagePullerror in Kubernetes. You can either do a manual override or wait for chart5.21.3.What's Changed
Fixes
*/finalizerspatch;update perms for OpenShift by @Baarsgaard in #2391Full Changelog: grafana/grafana-operator@v5.21.1...v5.21.2
v5.21.1Compare Source
NOTE: functionality-wise,
v5.21.1is the same asv5.21.0. - The patch release contains only a fix for our helm publishing workflow. Make sure to use5.21.1tag for helm chart.NOTE: due to a bug in our workflow,
image.repositoryin the helm chart is set toghcr.io/grafana/grafana-operator(instead ofgrafana/grafana-operator), which will lead to theErrImagePullerror in Kubernetes. You can either do a manual override or wait for chart5.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
vprefix from our chart versions which should hopefully simplify OCI installations. We also aligned theimage.repositoryvalue 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.repositoryfield to change the image, this field has been split intoregistryandrepositoryto 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.yamlcontained this:you'll need to replace it with this:
values.yaml, you can safely ignore this.Upgrade instructions
Using Helm
Using kubectl
Using kustomize
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
.spec.client.useKubeAuthby @Baarsgaard in #2137dandwinforduration strings by @vignesh-codes in #2269Fixes
.spec.editablecannot be be disabled by @Miguel-Barros96 in #2276CreateContainerConfigErrorwithdisableDefaultAdminSecretand admin secret missing by @Baarsgaard in #2356vprefix from Helm Chart version by @Baarsgaard in #2377Dependencies
d92957cby @renovate-sh-app[bot] in #22288c9accaby @renovate-sh-app[bot] in #2229bc988d5by @renovate-sh-app[bot] in #2230New Contributors
Full Changelog: grafana/grafana-operator@v5.20.0...v5.21.0
v5.21.0Compare 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
vprefix from our chart versions which should hopefully simplify OCI installations. We also aligned theimage.repositoryvalue 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.repositoryfield to change the image, this field has been split intoregistryandrepositoryto 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.yamlcontained this:you'll need to replace it with this:
values.yaml, you can safely ignore this.Upgrade instructions
Using Helm
Using kubectl
Using kustomize
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
.spec.client.useKubeAuthby @Baarsgaard in #2137dandwinforduration strings by @vignesh-codes in #2269Fixes
.spec.editablecannot be be disabled by @Miguel-Barros96 in #2276CreateContainerConfigErrorwithdisableDefaultAdminSecretand admin secret missing by @Baarsgaard in #2356vprefix from Helm Chart version by @Baarsgaard in #2377Dependencies
d92957cby @renovate-sh-app[bot] in #22288c9accaby @renovate-sh-app[bot] in #2229bc988d5by @renovate-sh-app[bot] in #2230New Contributors
Full Changelog: grafana/grafana-operator@v5.20.0...v5.21.0
v5.20.0Compare 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
latestas a plugin version) and implemented some long overdue bug fixes!Upgrade instructions
Using Helm
Using kubectl
Using kustomize
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.19.0...v5.20.0
v5.19.4Compare Source
v5.19.3Compare Source
v5.19.2Compare Source
v5.19.1Compare Source
v5.19.0Compare 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
Using kubectl
Using kustomize
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
.spec.suspend=trueby @Baarsgaard in #2066.spec.route.subdomainby @Baarsgaard in #2074Fixes
.spec.versionusing Patch to avoid Deployment spec drift by @Baarsgaard in #2037forto 0s by @Baarsgaard in #2094.spec.config.security.admin_*as fallback for external instances by @Baarsgaard in #2092Dependencies
99baf0dto v0.30.0 by @dependabot[bot] in #2012New 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.
This PR was generated by Mend Renovate. View the repository job log.