Documentation

Manage environment variables in your InfluxDB Cluster

Use environment variables to define settings for individual components in your InfluxDB cluster and adjust your cluster’s running configuration. Define environment variables for each component in your AppInstance resource.

InfluxDB Clustered components support various environment variables. While many of these variables have default settings, you can customize them by setting your own values.

Overriding default settings may affect overall cluster performance

InfluxDB Clustered components have complex interactions that can be affected when overriding default configuration settings. Changing these settings may impact overall cluster performance. Before making configuration changes using environment variables, consider consulting InfluxData Support to identify any potential unintended consequences.

AppInstance component schema

In your AppInstance resource, configure individual component settings in the spec.package.spec.components property if configuring your AppInstance resource directly or, if using Helm, use the components property in your values.yaml. This property supports the following InfluxDB Clustered component keys:

  • ingester
  • querier
  • router
  • compactor
  • garbage-collector
apiVersion: kubecfg.dev/v1alpha1
kind: AppInstance
metadata:
  name: influxdb
  namespace: influxdb
spec:
  package:
    # ...
    spec:
      components:
        ingester:
          # Ingester settings ...
        querier:
          # Querier settings ...
        router:
          # Router settings. ...
        compactor:
          # Compactor settings ...
        garbage-collector:
          # Garbage collector settings ...
# ...
components:
  ingester:
    # Ingester settings ...
  querier:
    # Querier settings ...
  router:
    # Router settings. ...
  compactor:
    # Compactor settings ...
  garbage-collector:
    # Garbage collector settings ...

For more information about components in the InfluxDB 3 storage engine, see the InfluxDB 3 storage engine architecture.

Set environment variables for a component

  1. Under the specific component property, use the <component>.template.containers.iox.env property to define environment variables.

  2. In the env property, structure each environment variable as a key-value pair where the key is the environment variable name and the value is the environment variable value (string-formatted). For example, to configure environment variables for the Garbage collector:

    apiVersion: kubecfg.dev/v1alpha1
    kind: AppInstance
    metadata:
      name: influxdb
      namespace: influxdb
    spec:
      package:
        # ...
        spec:
          components:
            garbage-collector:
              template:
                containers:
                  iox:
                    env:
                      INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h'
                      INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h'
    # ...
    components:
      garbage-collector:
        template:
          containers:
            iox:
              env:
                INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h'
                INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h'
  3. Apply the configuration changes to your cluster and add or update environment variables in each component.

    kubectl apply \
      --filename myinfluxdb.yml \
      --namespace influxdb
    helm upgrade \
      influxdata/influxdb3-clustered \
      -f ./values.yml \
      --namespace influxdb

Update environment variables instead of removing them

Most configuration settings that can be overridden by environment variables have default values that are used if the environment variable is unset. Removing environment variables from your AppInstance resource configuration will not remove those environment variables entirely; instead, they will revert to their default settings. To revert to the default settings, simply unset the environment variable or update the value in your AppInstance resource to the default value.

In the preceding example, the INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF environment variable is set to 6h. If you remove INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF from the env property, the cutoff reverts to its default setting of 30d.

View example of environment variables in all components


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2