Skip to content

perf-sentinel chart v0.11.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Aug 14:23
chart-v0.11.1
This tag was signed with the committer’s verified signature.
robintra Robin Trassard
SSH Key Fingerprint: PXKuwB2z5bZZ3oIp+fY+Xz6iV03G/e2xkgzJJxieD4k
Verified
Learn about vigilant mode.
c88de21

What's new in chart-v0.11.1

An appVersion move from 0.11.0 to 0.11.1, and nothing else. No template, value or default changes: a values file renders the same objects as 0.11.0 apart from the image tag, the chart version labels and the checksum they feed. Everything under Behavior is what the new daemon image does differently once it rolls, and this time it does nothing differently, both changes ride in the report the report and demo subcommands render.

Behavior

  • The upgrade rolls the pods. The image tag falls back to .Chart.AppVersion when image.tag is empty, which is the default, so the pod spec moves from 0.11.0 to 0.11.1. The checksum/config annotation also changes, since the ConfigMap carries the chart version in its labels. Pinning image.tag explicitly keeps the old image and skips the rollout entirely, at no cost here, since the daemon behaves identically either way.
  • The daemon is unaffected. No route, metric, wire format, config key or detection behaviour changes. /api/findings, /api/correlations, /metrics and the OTLP listeners answer exactly as they did under 0.11.0.
  • The HTML report names the deployment on every findings row. Findings separate by grouping since 0.11.0, but the list showed only the service and the endpoint, so the same problem in two namespaces produced two rows that looked identical. This is visible in a report rendered by perf-sentinel report, not in anything the daemon serves.
  • No acknowledgment needs re-capturing. Signatures are untouched on both the TOML baseline and the daemon's runtime store.
  • The archived per-window JSON keeps its shape. A disclosure content_hash computed under 0.11.0 still verifies here.

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

Upgrade an existing release:

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

Verify that the rollout picked up the new image:

kubectl get pod -l app.kubernetes.io/name=perf-sentinel \
  -o jsonpath='{.items[*].spec.containers[*].image}'

Read docs/HELM-DEPLOYMENT.md for the sizing guidance, the Ingress postures and the NetworkPolicy peer an ingress controller needs.

If you are upgrading from chart-v0.10.0 or earlier, read the chart-v0.11.0 notes first: that release repairs a duplicate scrape on StatefulSet deployments with a ServiceMonitor, splits findings by deployment, and carries a /metrics change worth checking if you scrape with vmagent.

Full Changelog: chart-v0.11.0...chart-v0.11.1

Assets 4
Loading