1 # InfluxDB v2 Helm chart
3 [InfluxDB](https://github.com/influxdata/influxdb) is an open source time series
4 database with no external dependencies. It's useful for recording metrics,
5 events, and performing analytics.
7 The InfluxDB v2 Helm chart uses the [Helm](https://helm.sh) package manager to
8 bootstrap an InfluxDB v2 StatefulSet and service on a
9 [Kubernetes](http://kubernetes.io) cluster.
15 - (Optional) PersistentVolume (PV) provisioner support in the underlying infrastructure
19 1. Add the InfluxData Helm repository:
22 helm repo add influxdata https://helm.influxdata.com/
25 2. Run the following command, providing a name for your InfluxDB release:
28 helm upgrade --install my-release influxdata/influxdb2
31 > **Tip**: `--install` can be shortened to `-i`.
33 This command deploys InfluxDB v2 on the Kubernetes cluster using the default configuration.
35 > **Tip**: To view all Helm chart releases, run `helm list`.
37 ## Uninstall the chart
39 To uninstall the `my-release` deployment, use the following command:
42 helm uninstall my-release
45 This command removes all Kubernetes components associated with the chart and deletes the release.
49 The [InfluxDB v2](https://hub.docker.com/_/influxdb/) image stores data in the `/var/lib/influxdb2` directory in the container.
51 If persistence is enabled, a [Persistent Volume](http://kubernetes.io/docs/user-guide/persistent-volumes/)
52 associated with StatefulSet is provisioned. The volume is created using dynamic
53 volume provisioning. In case of a disruption (for example, a node drain),
54 Kubernetes ensures that the same volume is reattached to the Pod, preventing any
55 data loss. However, when persistence is **not enabled**, InfluxDB data is stored
56 in an empty directory, so if a Pod restarts, data is lost.
58 Check out our [Slack channel](https://www.influxdata.com/slack) for support and information.
60 ## Fixed Auth Credentials
62 If you need to use fixed token and/or password you can set the values
63 `adminUser.password` and `adminUser.token` or you can use an existing secret,
64 which would be a better approach.
79 If you do not specify an existing secret, the admin-password and admin-token
80 will be automatically generated. They will remain consistent even after
85 By default this chart uses the docker hub influxdb image which includes an
86 entrypoint for automatically setting up InfluxDB. This operation is idempotent
87 and will be skipped if a boltdb is found on startup.
89 For more information see "Automated Setup" in the [docker image README](https://hub.docker.com/_/influxdb).
91 For configuration options see `adminUser` in `values.yaml`.
95 Extra environment variables can be passed influxdb using `.Values.env`. For