Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Open source

Configure Grafana Agent in flow mode on Kubernetes

To configure Grafana Agent in flow mode on Kubernetes, perform the following steps:

  1. Download a local copy of values.yaml for the Helm chart.

  2. Make changes to your copy of values.yaml to customize settings for the Helm chart.

    Refer to the inline documentation in the values.yaml for more information about each option.

  3. Run the following command in a terminal to upgrade your Grafana Agent installation:

    helm upgrade RELEASE_NAME grafana/grafana-agent -f VALUES_PATH
    1. Replace RELEASE_NAME with the name you used for your Grafana Agent installation.

    2. Replace VALUES_PATH with the path to your copy of values.yaml to use.

Kustomize considerations

If you are using Kustomize to inflate and install the Helm chart, be careful when using a configMapGenerator to generate the ConfigMap containing the configuration. By default, the generator appends a hash to the name and patches the resource mentioning it, triggering a rolling update.

This behavior is undesirable for Grafana Agent because the startup time can be significant depending on the size of the Write-Ahead Log. You can use the Helm chart sidecar container to watch the ConfigMap and trigger a dynamic reload.

The following is an example snippet of a kustomization that disables this behavior:

  - name: grafana-agent
      - config.river
      disableNameSuffixHash: true