Deploy InfluxDB 3 Enterprise on Kubernetes
Use the official InfluxDB 3 Enterprise Helm chart to deploy InfluxDB 3 Enterprise on Kubernetes. The Helm chart packages recommended deployment patterns into a single chart, eliminating the need to maintain custom manifests or configure deployments from scratch.
Beta status
The InfluxDB 3 Enterprise Helm chart is currently in beta. During this phase, InfluxData is refining defaults and ensuring upgrades behave as operators expect. Find support for InfluxDB 3 Enterprise or report a Helm chart issue.
- Key features
- Prerequisites
- Install the Helm chart
- Configuration options
- Upgrade the deployment
- Uninstall
- Troubleshooting
- Report an issue with Helm charts
- Find support
Key features
- Simplified deployment: Deploy InfluxDB 3 Enterprise with a single Helm chart instead of maintaining custom Kubernetes manifests
- Production patterns: Includes recommended configurations for object storage, cluster settings, and environment-specific overrides
- Standard Helm workflows: Use familiar Helm mechanisms for installs, upgrades, and rollouts
- Environment overrides: Customize deployments for different environments (development, staging, production)
Prerequisites
Before deploying InfluxDB 3 Enterprise on Kubernetes, ensure you have:
- A Kubernetes cluster (version 1.25 or later)
- Helm installed (version 3.0 or later)
kubectlconfigured to access your cluster- Object storage configured (Amazon S3, Azure Blob Storage, Google Cloud Storage, or S3-compatible storage such as MinIO)
Licensing
InfluxDB 3 Enterprise requires a license to run. For more information about license types, activation, and management, see Manage your InfluxDB 3 Enterprise license.
Install the Helm chart
Add the InfluxData Helm repository:
helm repo add influxdata https://helm.influxdata.com/Update your Helm repositories:
helm repo updateCreate a namespace for InfluxDB:
kubectl create namespace influxdbCreate a
values.yamlfile with your configuration. See Configuration options for available settings.Install the chart:
helm install influxdb3-enterprise influxdata/influxdb3-enterprise \ --namespace influxdb \ --values values.yamlVerify the deployment:
kubectl get pods --namespace influxdb
Configuration options
The Helm chart supports common production configurations through the values.yaml file.
Download the default values file as a starting point:
curl -O https://raw.githubusercontent.com/influxdata/helm-charts/master/charts/influxdb3-enterprise/values.yamlObject storage
Configure object storage for Parquet file storage. InfluxDB 3 Enterprise supports Amazon S3, Azure Blob Storage, Google Cloud Storage, and S3-compatible storage.
Configure Amazon S3 as your object store:
objectStore:
type: s3
bucket: S3_BUCKET
region: S3_REGION
accessKey: S3_ACCESS_KEY
secretKey: S3_SECRET_KEYReplace the following:
S3_BUCKET: your S3 bucket nameS3_REGION: AWS region (for example,us-east-1)S3_ACCESS_KEY: AWS access key IDS3_SECRET_KEY: AWS secret access key
Configure Azure Blob Storage as your object store:
objectStore:
type: azure
bucket: AZURE_CONTAINER
account: AZURE_ACCOUNT
accessKey: AZURE_ACCESS_KEYReplace the following:
AZURE_CONTAINER: your Azure container nameAZURE_ACCOUNT: Azure storage account nameAZURE_ACCESS_KEY: Azure storage access key
Configure Google Cloud Storage as your object store:
objectStore:
type: gcs
bucket: GCS_BUCKET
serviceAccountSecret:
name: gcs-credentials
key: credentials.jsonReplace GCS_BUCKET
with your Google Cloud Storage bucket name.
Create a Kubernetes secret with your service account credentials:
kubectl create secret generic gcs-credentials \
--from-file=credentials.json=/path/to/service-account.json \
--namespace influxdbConfigure S3-compatible storage (such as MinIO) as your object store:
objectStore:
type: s3
bucket: MINIO_BUCKET
endpoint: MINIO_ENDPOINT
accessKey: MINIO_ACCESS_KEY
secretKey: MINIO_SECRET_KEY
forcePathStyle: trueReplace the following:
MINIO_BUCKET: your MinIO bucket nameMINIO_ENDPOINT: MinIO endpoint URL (for example,http://minio.minio.svc:9000)MINIO_ACCESS_KEY: MinIO access keyMINIO_SECRET_KEY: MinIO secret key
Cluster configuration
Configure cluster-level settings:
# Cluster name
clusterName: my-influxdb-cluster
# Resource limits and requests
resources:
limits:
cpu: "4"
memory: 8Gi
requests:
cpu: "2"
memory: 4Gi
# Persistent storage for Write-Ahead Log (WAL)
persistence:
enabled: true
size: 10Gi
storageClass: standardIngress
Configure ingress to expose the InfluxDB API:
ingress:
enabled: true
hosts:
- INFLUXDB_HOST
tls:
- secretName: influxdb-tls
hosts:
- INFLUXDB_HOSTReplace INFLUXDB_HOST
with your InfluxDB hostname (for example, influxdb.example.com).
Upgrade the deployment
To upgrade your deployment after modifying values.yaml:
helm upgrade influxdb3-enterprise influxdata/influxdb3-enterprise \
--namespace influxdb \
--values values.yamlTo upgrade to a new chart version:
helm repo update
helm upgrade influxdb3-enterprise influxdata/influxdb3-enterprise \
--namespace influxdb \
--values values.yamlUninstall
To remove the InfluxDB deployment:
helm uninstall influxdb3-enterprise --namespace influxdbUninstalling the Helm release does not delete persistent volumes or data in object storage. To remove all data, manually delete the persistent volume claims and object storage bucket.
Troubleshooting
View pod logs
To view logs from the InfluxDB pod:
kubectl logs -l app.kubernetes.io/name=influxdb3-enterprise \
--namespace influxdbCheck pod status
To check the status of InfluxDB pods:
kubectl get pods --namespace influxdb -o wideDescribe pod for events
To see detailed information and events for a pod:
kubectl describe pod POD_NAME --namespace influxdbReplace POD_NAME
with the name of the pod (from kubectl get pods).
Report an issue with Helm charts
For Helm chart issues or feedback, see the Helm charts repository issues page.
Find support
The InfluxDB Discord server is the best place to find community support for InfluxDB 3 Enterprise. Customers with a commercial license can contact InfluxData Support.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB 3 Enterprise and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support. Customers using a trial license can email trial@influxdata.com for assistance.