robintra/perf-sentinel chart-v0.25.4

perf-sentinel chart v0.25.4

on GitHub

What's new in chart-v0.25.4

A metadata-only bump. No template changes, no values.yaml key added or removed, and the rendered perf-sentinel.toml is byte-for-byte what chart-v0.25.3 rendered, same 5036 bytes and the same digest under the default values. appVersion moves to 0.25.4 and image.tag follows it to :0.25.4, which is the whole of this release: everything it ships is inside the daemon image.

What moves inside the pod

Nothing the daemon serves. Its API, its metrics and the findings it stores and exports keep the same fields and values, and no finding changes signature. What changes is how the perf-sentinel binary prints a finding's code location in its text outputs. A function name that already carries its namespace, as the stable code.function.name attribute sends it, prints once instead of twice, a PHP, Rust, C++ or Ruby namespace joins its function with ::, and an empty attribute no longer leaves a stray separator. Against a daemon, that reaches the detail panel of perf-sentinel query inspect.

Compared with the 0.25.3 binary on eleven code location shapes, both versions emit the same findings, signatures, endpoints and SARIF locations, and only the printed line differs.

The v0.25.4 binary notes describe the three changes.

Upgrade impact

• Pods roll on the image. helm upgrade replaces them because appVersion and image.tag move together.
• Acknowledgments keep matching. No finding appears, disappears or changes signature, so perf_sentinel_findings_total reads as before.
• The example findings dashboard lives outside this chart and moves to version 13. Its Findings, Incident findings and Findings history tables name each finding's call site in a Code column, read from the code_location every finding already carries, so a 0.25.3 daemon fills it too. Re-import it where it is provisioned.
• checksum/config moves too, and not because your configuration changed. The rendered perf-sentinel.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 differs on every version bump.
• No values.yaml key is added or removed, no template changes, and the shipped PrometheusRule is untouched.

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.25.4

Upgrade an existing release:

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

Read docs/HELM-DEPLOYMENT.md for the ServiceMonitor section, sizing and Ingress postures.

If you are upgrading from chart-v0.23.0 or earlier, read the chart-v0.24.0 notes first: that release raises the default workload.statefulset.persistence.size to 2Gi, which an existing StatefulSet does not pick up on its own. From chart-v0.18.0 or earlier, read the chart-v0.19.0 notes as well: 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, the chart-v0.17.0 notes change the shipped PrometheusRule.

Full Changelog: chart-v0.25.3...chart-v0.25.4