Skip to content

Latest commit

 

History

History
72 lines (43 loc) · 2.33 KB

README.md

File metadata and controls

72 lines (43 loc) · 2.33 KB
Raw

InfluxDB

An Open-Source Time Series Database

InfluxDB is an open source time series database built by the folks over at InfluxData with no external dependencies. It's useful for recording metrics, events, and performing analytics.

QuickStart

$ helm install stable/influxdb --name foo --namespace bar

Introduction

This chart bootstraps an InfluxDB deployment and service on a Kubernetes cluster using the Helm Package manager.

Prerequisites

  • Kubernetes 1.4+
  • PV provisioner support in the underlying infrastructure (optional)

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release stable/influxdb

The command deploys InfluxDB on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release --purge

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The default configuration values for this chart are listed in values.yaml.

The full image documentation contains more information about running InfluxDB in docker.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set persistence.enabled=true,persistence.size=200Gi \
    stable/influxdb

The above command enables persistence and changes the size of the requested data volume to 200GB.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml stable/influxdb

Tip: You can use the default values.yaml

Persistence

The InfluxDB image stores data in the /var/lib/influxdb directory in the container.

The chart mounts a Persistent Volume volume at this location. The volume is created using dynamic volume provisioning.