Deploy InfluxDB on Kubernetes: Time-Series Database

Deploy InfluxDB on Kubernetes to process time-series metrics, telemetry, and real-time analytics. Running InfluxDB as a StatefulSet ensures persistent data storage and reliable network identity across container restarts. This setup provisions a single-replica InfluxDB instance with automated initial setup, internal ClusterIP service routing, and HTTP health probes.

What's Included

Component	Type	Port	Role
influxdb	Namespace	N/A	Isolates InfluxDB resources
influxdb-config	ConfigMap	N/A	Holds custom InfluxDB runtime configuration options
influxdb	Service	8086	Exposes InfluxDB HTTP API internally via ClusterIP
influxdb	StatefulSet	8086	Runs single-replica InfluxDB 2.7 engine container
influxdb-storage	PersistentVolumeClaim	N/A	Provisions 10Gi persistent volume for metric engine storage
influxdb-secret	Secret	N/A	Stores initialization credentials, org, bucket, and token

Architecture Overview

The InfluxDB StatefulSet executes a single container running InfluxDB. Initialization parameters, including administrative credentials, organization name, default bucket, and API token, load directly from the Secret. The ClusterIP Service exposes HTTP API port 8086 inside the cluster, while HTTP GET probes continuously monitor the /health endpoint for startup, readiness, and liveness states.

Prerequisites

Active Kubernetes cluster with dynamic PersistentVolume provisioning supported.
Default StorageClass available to fulfill the ReadWriteOnce storage request.
KubeKanvas CLI installed and running on your computer (Optional, if you want to use one-click deployment)

How to Deploy

Verify target namespace settings or retain the default influxdb namespace.
Update initial username, password, token, organization, and bucket variables inside influxdb-secret.
Adjust the storage request in the volumeClaimTemplates block if higher volume capacity is needed.
Add custom engine parameters to influxdb-config if default settings require overrides.
Deploy the template to your cluster via the Play button in the top right bar. If you prefer to deploy manually, download the YAML and apply it with kubectl.
Wait for all pods to reach Running status. You can monitor progress in the Release Monitor screen.

How to Test

Verify HTTP endpoint readiness by running kubectl exec -n influxdb-ansar statefulset/influxdb -- curl -i http://localhost:8086/health.
Check InfluxDB CLI status by running kubectl exec -n influxdb-ansar statefulset/influxdb -- influx ping.
Query database buckets using kubectl exec -n influxdb-ansar statefulset/influxdb -- influx bucket list -o kubekanvas -t my-super-secret-token.

Use Cases

Application Performance Monitoring: Collect, store, and analyze application performance metrics in real time.
IoT Sensor Telemetry: Ingest high-frequency time-series data streams from edge devices and connected sensors.
Kubernetes Infrastructure Metrics: Act as a centralized backend for cluster metric collection and Grafana visualization.

Summary

This template configures a secure InfluxDB 2.7 deployment on Kubernetes using a StatefulSet, persistent storage volume, automated initial setup credentials, and HTTP health probes.

Tags:

TSDBInfluxDBKubernetesKubekanvasMonitoringGrafana

Created by:

Siddiqui

Deploy InfluxDB on Kubernetes: Time-Series Database template preview

0 uses

What's Included

Component	Type	Port	Role
influxdb	Namespace	N/A	Isolates InfluxDB resources
influxdb-config	ConfigMap	N/A	Holds custom InfluxDB runtime configuration options
influxdb	Service	8086	Exposes InfluxDB HTTP API internally via ClusterIP
influxdb	StatefulSet	8086	Runs single-replica InfluxDB 2.7 engine container
influxdb-storage	PersistentVolumeClaim	N/A	Provisions 10Gi persistent volume for metric engine storage
influxdb-secret	Secret	N/A	Stores initialization credentials, org, bucket, and token

Architecture Overview

How to Deploy

Verify target namespace settings or retain the default influxdb namespace.

Update initial username, password, token, organization, and bucket variables inside influxdb-secret.

Adjust the storage request in the volumeClaimTemplates block if higher volume capacity is needed.

Add custom engine parameters to influxdb-config if default settings require overrides.

Deploy the template to your cluster via the Play button in the top right bar. If you prefer to deploy manually, download the YAML and apply it with kubectl.

Wait for all pods to reach Running status. You can monitor progress in the Release Monitor screen.

How to Test

Verify HTTP endpoint readiness by running kubectl exec -n influxdb-ansar statefulset/influxdb -- curl -i http://localhost:8086/health.

Check InfluxDB CLI status by running kubectl exec -n influxdb-ansar statefulset/influxdb -- influx ping.

Query database buckets using kubectl exec -n influxdb-ansar statefulset/influxdb -- influx bucket list -o kubekanvas -t my-super-secret-token.

Use Cases

Application Performance Monitoring: Collect, store, and analyze application performance metrics in real time.

IoT Sensor Telemetry: Ingest high-frequency time-series data streams from edge devices and connected sensors.

Kubernetes Infrastructure Metrics: Act as a centralized backend for cluster metric collection and Grafana visualization.