Documentation

InfluxDB Clustered

Install InfluxDB Clustered

InfluxDB Clustered is deployed and managed using Kubernetes. This installation guide walks you through the following four installation phases and the goal of each phase. This process helps you set up and run your cluster and ensure it performs well with your expected production workload.

  1. Set up your cluster: Get a basic InfluxDB cluster up and running with as few external dependencies as possible and confirm you can write and query data.
  2. Customize your cluster: Review and customize the available configuration options specific to your workload.
  3. Optimize your cluster: Scale and load test your InfluxDB cluster to confirm that it will satisfy your scalability and performance needs. Work with InfluxData to review your schema and determine how best to organize your data and develop queries representative of your workload to ensure queries meet performance requirements.
  4. Secure your cluster: Integrate InfluxDB with your identity provider to manage access to your cluster. Install TLS certificates and enable TLS access. Prepare your cluster for production use.

InfluxDB Clustered license

InfluxDB Clustered is a commercial product offered by InfluxData, the creators of InfluxDB. Please contact InfluxData Sales to obtain a license before installing InfluxDB Clustered.

Contact InfluxData Sales

Setup, configure, and deploy InfluxDB Clustered

Deploying in air-gapped environments

To deploy InfluxDB Clustered in an air-gapped environment (without internet access), use one of the following approaches:

  • Recommended: Directly use kubit local apply
  • Helm (includes the kubit operator)
  • Directly use the kubit operator

For more information, see Choose the right deployment tool for your environment

  1. Set up your InfluxDB cluster
  2. Customize your InfluxDB cluster
  3. Optimize your InfluxDB cluster
  4. Secure your InfluxDB cluster

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

What is your InfluxDB cluster URL?

Enter your InfluxDB cluster URL and we’ll update code examples for you.

Enter cluster URL

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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