Kubernetes is a popular way to deploy and manage containers across multiple servers and cloud providers.

This page is about using Kubernetes with the TICK stack and 1.x versions of InfluxDB. To install InfluxDB 2.x and Kubernetes, see the Kubernetes tab in Install InfluxDB v2.

Use InfluxData platform and Kubernetes to do the following:

Monitor Kubernetes

Use the TICK stack to monitor services that make up a Kubernetes cluster, whether you’re running InfluxDB in a Kubernetes cluster or somewhere else. Do the following to monitor Kubernetes:

Use the kube-influxdb project

The kube-influxdb project is a set of Helm charts to make collection and visualization of Kubernetes metrics easy. It uses Telegraf, the metrics collection agent, to collect metrics and events and includes a set of pre-configured Chronograf dashboards.

See the kube-influxdb Getting Started guide.

Collect Kubernetes metrics with Telegraf

Use Telegraf to collect metrics in a Kubernetes cluster, including Docker container metrics and stats from kubelets. Or use Telegraf to scrape Prometheus metrics API endpoints. Telegraf is used in the kube-influxdb project to collect metrics.

See Set up a Kubernetes monitoring architecture using Telegraf.

Use the Prometheus remote read and write API

Use the Prometheus remote read and write API for clusters already using Prometheus for metrics collection. For more information, see Prometheus remote read and write API support in InfluxDB.

Deploy the TICK stack in Kubernetes

To install and configure the open source TICK stack–Telegraf, InfluxDB, Chronograf, and Kapacitor–in Kubernetes, do one of the following:

Use Helm charts

InfluxData maintains Helm charts for setting up data collection and monitoring in Kubernetes using InfluxDB and related applications.

Use K8s operator

The InfluxData operator is a Kubernetes operator. Use the InfluxData operator to deploy InfluxDB in Kubernetes and handle operational tasks automatically, like creating a backup. The operator has been tested on AWS’s Elastic Kubernetes Service and GCP’s Google Kubernetes Engine.

Deploy InfluxDB using the InfluxData operator

Use solutions for Kubernetes services

InfluxData maintains ways to deploy the InfluxData Platform components to popular Kubernetes service providers.

Frequently asked questions

How is the InfluxData platform (TICK) different from Prometheus?

InfluxDB is specifically built to handle time series data. InfluxDB handles string data types and event data that occurs in irregular intervals, including structured logs, application events, and tracing data.

How should I run InfluxDB in Kubernetes?

InfluxData provides several ways to deploy InfluxDB in Kubernetes. For a declarative way to deploy InfluxDB, we recommend exploring the Terraform InfluxDB module.

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: