github kuvasz-uptime/kuvasz 4.8.0
v4.8.0

55 minutes ago

Documentation: v4.8.0- kuvasz-uptime.dev

docker pull kuvaszmonitoring/kuvasz:4.8.0

Important

Make your voice heard!

There is a short questionnaire about Kuvasz in general, which you can fill out anonymously. It takes only a few minutes, and your feedback is highly appreciated as it helps me to focus on the most important features and improvements in the future. You can find it here.

Thanks, Adam

Features

  • Display names for the monitors: every monitor can have an optional display-name now, which is shown instead of its name on the Web UI, on the status pages and in the notifications. Unlike the name, it doesn't have to be unique, and you can change it at any time. This is especially useful if you manage your monitors in a YAML file: so far, the only way to change how a monitor was shown was to rename it, but a renamed monitor is a new one, so the old one was deleted with its whole history. Now you can keep the name, and change only the display name. The Web UI still shows the name next to the display name, because the YAML file, the status pages and the maintenance windows refer to the monitor by its name. The display name is also available in the API (displayName) and in the backups, the search by name finds it too, and the webhooks get a new monitorLabel field, which holds the display name, or the name if the monitor has no display name (#590).
  • Sender name for the email integration: an email integration can have a from-name now, which is shown as the display name of the sender in the "From" field of the notifications. If you don't set it, nothing changes: the address is used as the name, as before. The name is also returned by the API (fromName) and shown on the Integrations page.
  • More HTTPRoutes in the Helm chart: the chart can create more Gateway API routes with extraHttpRoutes, besides the one in httpRoute. This way, you can expose Kuvasz on more Gateways with different rules. For example, it can serve everything on an internal Gateway, and only a status page on a public one. Check the Helm deployment guide for an example (#589).

Fixes

  • The HTTPRoute of the Helm chart was always out of sync in Argo CD: Kubernetes fills in the group and kind fields of the route's backend and Gateway, even if they are not set. The chart didn't set them, so tools that compare the chart with what is actually running in the cluster (like Argo CD) always saw a difference. The chart sets these fields now for the backend, and for the default Gateway (used when httpRoute.parentRefs is empty). Nothing changes in your cluster. If you set your own values for the route, like httpRoute.parentRefs or httpRoute.extraRules, check the Helm deployment guide for the fields to add to them (#587).
  • The Helm chart changed the admin password on every upgrade: if you didn't set auth.adminUser or auth.adminPassword, the chart created new random values for them every time you ran helm upgrade. So the credentials you got after the install stopped working, and the pod restarted on every upgrade. Now the chart creates them only once, and keeps them on upgrades. If you use a tool that creates the manifests with helm template (like Argo CD), the chart can't read the existing values, so set them yourself, or use your own Secret. Check the Helm deployment guide for the details (#588).
  • The minimum Helm version was wrong in the documentation: the Helm deployment guide said that you need Helm 4, and the README of the chart said Helm 3.2.0. The chart is published to an OCI registry, and Helm can install charts from there without extra settings only from version 3.8.0. So the minimum version is Helm 3.8.0 now in both places, and Helm 4 works too.

Full changelog: 4.7.0...4.8.0

Don't miss a new kuvasz release

NewReleases is sending notifications on new releases.