Documentation

Configure your InfluxDB cluster

InfluxDB Clustered deployments are managed using Kubernetes and configured using a YAML configuration file. Apply configuration settings to your cluster by editing and applying a Kubernetes custom resource (CRD) called AppInstance. The AppInstance CRD is defined in a YAML file (use the example-customer.yml provided by InfluxData as a template).

We recommend editing the AppInstance resource directly as the primary method for configuring and managing your InfluxDB cluster. After you have edited your AppInstance, use the kubit CLI or kubectl deployment tool, depending on your requirements.

If you are required to use Helm, there is an InfluxDB Clustered Helm chart available that acts as a wrapper for the AppInstance resource and lets you use Helm to manage configuration changes in your InfluxDB cluster.

Choose the right deployment tool for your environment


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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