perf-sentinel chart v0.2.39

What's new in chart-v0.2.39

This is a metadata-only chart bump: appVersion advances from 0.7.3 to 0.7.4, the default image.tag now resolves to ghcr.io/robintra/perf-sentinel:0.7.4, and the artifacthub.io/changes annotation refreshes to surface the two new opt-in energy sources on Artifact Hub. No chart-level template diff, no values.yaml schema change, no new RBAC, no new optional ConfigMap or Secret, no .perf-sentinel.toml review required to upgrade. The chart-v0.2.38 surface is preserved byte-for-byte.

The 0.7.4 daemon image adds two new opt-in measured-energy backends to the carbon attribution stack and refreshes the documentation tree. Kepler eBPF ([green.kepler]) gives ARM64 hosts (Graviton, Ampere, Cobalt 100, Apple Silicon) a measured path that Scaphandre RAPL cannot serve. Redfish BMC ([green.redfish]) gives bare-metal nodes a real wall-plug measurement including periphery (PSU, NIC, drives, fans). Full release notes for the daemon at v0.7.4. None of these changes touches a chart-level template, a daemon HTTP route, a Prometheus metric label set the chart already exposes, or the OTLP listener wire format.

Changed

• appVersion bumped from 0.7.3 to 0.7.4, default image.tag now resolves to ghcr.io/robintra/perf-sentinel:0.7.4.
• artifacthub.io/changes annotation refreshed to surface the new Kepler and Redfish backends on Artifact Hub.
• No chart-level config change. values.yaml, every template, the ServiceMonitor rendering, the NetworkPolicy rendering, the optional [daemon.ack] and [daemon.cors] plumbing, and the ack-toml-baseline mount are byte-for-byte identical to chart-v0.2.38.

Behavior

• Daemon binary side: two new opt-in energy sources. Both [green.kepler] and [green.redfish] are absent from the default config, so existing deployments behave identically at upgrade time. Operators that want the new measured path on ARM64 or bare-metal nodes add the relevant section to .perf-sentinel.toml (mounted via the existing chart values) and the scraper engages on the next daemon restart.
• Daemon binary side: carbon precedence chain extended. New order, electricity_maps_api > scaphandre_rapl > kepler_ebpf > redfish_bmc > cloud_specpower > io_proxy_v3 > io_proxy_v2 > io_proxy_v1. A service already served by Scaphandre keeps Scaphandre even when Kepler or Redfish is configured, no existing measured-energy mapping is overridden.
• Daemon binary side: two new Prometheus gauges. perf_sentinel_kepler_last_scrape_age_seconds and perf_sentinel_redfish_last_scrape_age_seconds are exposed on the existing /metrics endpoint. They only emit when the corresponding scraper is configured, so the ServiceMonitor scrape continues to return the same line set on a default install.
• Daemon binary side: new co2.model enum values. The model tag field gains kepler_ebpf and redfish_bmc. The field is already documented as an open string set populated dynamically, so v0.7.3 consumers parsing periodic disclosures continue to work without changes.
• No HTTP-shape change. Every /api/* route, every existing /metrics line, the OTLP HTTP and gRPC routes, and every JSON shape are byte-for-byte identical to chart-v0.2.38 for already-clean inputs.
• No upgrade hook required, no on-disk migration. The runtime ack store JSONL schema is unchanged. Existing acks survive the upgrade.

Install

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

Upgrade an existing release:

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

The bump is metadata-only on the chart side. The new daemon binary brings two opt-in energy backends that engage only when the operator adds [green.kepler] or [green.redfish] to .perf-sentinel.toml. Existing deployments without these sections see no carbon score change at the upgrade boundary. ARM64 operators previously stuck on the proxy fallback now have a measured path documented in docs/LIMITATIONS.md "Kepler precision bounds" and "Redfish BMC precision bounds".

Full Changelog: chart-v0.2.38...chart-v0.2.39