[jtslear]

What

grafana-agent is EOL. This swaps the grafana-agent subchart for the grafana/alloy chart (1.13.1, app v1.20.1) and renames the values key from grafana-agent to alloy.

• Chart.yaml / Chart.lock: alloy dependency replaces grafana-agent.
• values.yaml: alloy: block keeps the same collector ConfigMap, clustering, mounts and daemonset annotation. Drops agent.mode: flow, which Alloy doesn't have.
• Templates: the collector ConfigMap, the relabel helpers and the status dashboard read the alloy values. The job label becomes <ns>/alloy/alloy and the metric becomes alloy_config_last_load_successful.
• Docs: README, README.gotmpl, TESTING_KIND.md and CHANGELOG updated. compiled/resources.yaml regenerated.

% helm search repo grafana alloy
NAME                    CHART VERSION   APP VERSION     DESCRIPTION
grafana/alloy           1.13.1          v1.20.1         Grafana Alloy

Breaking changes

• Rename any grafana-agent: values overrides to alloy:.
• Pod job label changes from <ns>/grafana-agent/grafana-agent to <ns>/alloy/alloy. Queries and alerts on the old label need updating.
• Alloy listens on 12345 instead of 80. Pod discovery uses the http-metrics named port, so scraping is unaffected.

Notes

• The River collector config is unchanged. alloy validate --stability.level=generally-available passes on the rendered config against grafana/alloy:v1.20.1.
• Alloy's cluster join address is now alloy-cluster, rendered by the chart.
• Resource requests/limits are not set, matching the previous grafana-agent config in this chart.
• Chart version is not bumped in this PR; it's set from the release tag at publish time (intended release: publish-minor, 0.8.0).

Reference:

• https://grafana.com/blog/grafana-agent-to-grafana-alloy-opentelemetry-collector-faq/

[dannykopping]

LGTM; have you tested that it all works fine?

[dannykopping]

We can make it listen on any port we want; maybe let's export both?

[jtslear]

@dannykopping my testing consisted of the following:

Kind cluster running version 0.7.5 (current latest), this confirmed current behavior and that the grafana-agent was in use. I then pulled this branch, ran the helm upgrade, confirmed alloy replaced. On reaching out to the port, the service was operating just fine and it looks like a copy and paste of grafana-agent, the service looks and operated the same, but did include a fancy chart. But the grafana-agent items were completely missing as expected.

[dannykopping]

Great stuff, thanks @jtslear!