github robintra/perf-sentinel chart-v0.21.0
perf-sentinel chart v0.21.0

3 hours ago

What's new in chart-v0.21.0

A metadata-only bump. No template changes, no values.yaml key added or removed, and the rendered config.toml is byte-for-byte what chart-v0.20.2 rendered. appVersion moves to 0.21.0 and image.tag follows it to :0.21.0, which is the whole of this release: everything it ships is inside the daemon image.

What moves inside the pod

The daemon gains two query parameters on GET /api/findings. grouping is an exact match on the value the grouping Prometheus label has carried since 0.19.0, so label_values(perf_sentinel_findings_total, grouping) drives the listing with no conversion, and offset walks a fleet past the 1000-row page cap. An empty or blank filter value now means no filter, where it used to be an exact match on the empty string, which is what lets a Grafana All option reach an exact-match API.

The folded read behind that listing clones only the rows a page keeps, which on a 100 000-instance ring folding into 4300 signatures takes a one-row read from 9.2 ms to 5.9 ms, all of it under the read lock the write path waits behind. A serialized_calls suggestion names the block instead of carrying it, three distinct templates cut at 120 characters rather than every call of the sequence.

The v0.21.0 binary notes describe all of it, including the two behaviour changes a client can see.

Upgrade impact

  • Pods roll on the image. helm upgrade replaces them because appVersion and image.tag move together.
  • checksum/config moves too, and not because your configuration changed. The rendered config.toml is identical, but the ConfigMap carries helm.sh/chart and app.kubernetes.io/version labels that bump with the chart, so the checksum over it is different on every version bump. Nothing in the daemon's configuration is re-read differently.
  • No values.yaml key is added or removed, no template changes, and the shipped PrometheusRule is untouched.
  • The daemon's MSRV moves to 1.98.1, which matters only if you build the binary yourself. The published image is unaffected.

Install

The chart is published as an OCI artifact on GHCR, install it directly with no helm repo add step:

helm install perf-sentinel oci://ghcr.io/robintra/charts/perf-sentinel --version 0.21.0

Upgrade an existing release:

helm upgrade perf-sentinel oci://ghcr.io/robintra/charts/perf-sentinel --version 0.21.0

Read docs/HELM-DEPLOYMENT.md for the ServiceMonitor section, sizing and Ingress postures. Sizing is worth a second look on this release: the daemon's resident memory is set by max_retained_findings, not by the idle figure, and the README now carries a 7-day production reading to size a pod from.

If you are upgrading from chart-v0.18.0 or earlier, read the chart-v0.19.0 notes first: that release adds a grouping label to five metrics and is breaking for an unaggregated alert on any of them. From chart-v0.16.0 or earlier, read the chart-v0.17.0 notes as well, which drop the shipped PrometheusRule from seven alerts to five.

Full Changelog: chart-v0.20.2...chart-v0.21.0

Don't miss a new perf-sentinel release

NewReleases is sending notifications on new releases.