OpenTSDB

The OpenTSDB Helm chart enables the deployment of OpenTSDB, a scalable time-series database, in a Kubernetes cluster. OpenTSDB is designed for large-scale data collection, storage, and analysis, providing an efficient way to handle time-series data.

Prerequisites

• Kubernetes 1.19+
• Helm 3+

Add Helm Repository

Add the Helm repository to your local setup:

helm repo add zopdev https://helm.zop.dev
helm repo update

Refer to the Helm Repository Documentation for more information.

Install Helm Chart

To install the OpenTSDB Helm chart, use the following command:

helm install [RELEASE_NAME] zopdev/opentsdb

Replace [RELEASE_NAME] with your desired release name. For example:

helm install my-opentsdb zopdev/opentsdb

To customize configurations, provide a values.yaml file or override values via the command line.

Refer to Helm Install Documentation for more details.

Uninstall Helm Chart

To uninstall the OpenTSDB Helm chart and remove all associated Kubernetes resources, use the command:

helm uninstall [RELEASE_NAME]

For example:

helm uninstall my-opentsdb

See Helm Uninstall Documentation for additional details.

Configuration

Below is a summary of configurable parameters for the OpenTSDB Helm chart:

You can override these values in a values.yaml file or via the command line during installation.

Example values.yaml File

version: "v0.0.1"

resources:
  requests:
    cpu: "500m"
    memory: "1000Mi"
  limits:
    cpu: "1000m"
    memory: "2000Mi"

diskSize: "10Gi"

zookeeper:
  replicaCount: 1
  diskSize: "10Gi"
  resources:
    requests:
      cpu: "100m"
      memory: "500Mi"
    limits:
      cpu: "500m"
      memory: "1000Mi"

Apply the configuration file during installation:

helm install my-opentsdb zopdev/opentsdb -f values.yaml

Features

• Scalable Deployment: Adjust replica count for high availability and load distribution.
• Custom Resource Allocation: Define resource requests and limits for CPU and memory to suit workload requirements.
• Persistent Storage: Ensure data persistence using configurable persistent volumes.
• Rolling Updates: Apply changes to the StatefulSet with zero downtime using the RollingUpdate strategy.
• Bundled Zookeeper: Includes the ZopDev Zookeeper chart as a dependency — no external Zookeeper setup required.

Advanced Usage

Persistent Volume Configuration

Customize the persistent volume size for OpenTSDB data:

diskSize: "50Gi"

Pod Scheduling

nodeSelector, tolerations and affinity are passed straight through to the pod spec. All three are empty by default and render nothing, so leaving them unset changes nothing for an existing release.

Together they place the workload on a dedicated node pool — the nodeSelector picks the pool, the toleration gets past its taint:

nodeSelector:
  workload: stateful

tolerations:
  - key: workload
    operator: Equal
    value: stateful
    effect: NoSchedule

affinity takes a full Affinity object and is rendered verbatim.

These keys reach this chart’s own pods only. The bundled zookeeper subchart is pinned to v0.0.2, which predates this feature, so its pods cannot currently be pinned — setting zookeeper.nodeSelector is accepted and silently ignored. Bumping the zookeeper dependency to v0.0.3 or later is what makes it work.

Contributing

We welcome contributions to improve this Helm chart. Please refer to the CONTRIBUTING.md file for contribution guidelines.

Code of Conduct

To maintain a healthy and collaborative community, please adhere to our Code of Conduct.

License

This project is licensed under the LICENSE. Please review it for terms of use.

Connection Config

• OPENTSDB_HOST : Hostname or service name for the OpenTSDB server.
• OPENTSDB_PORT : Port number to connect to OpenTSDB. Defaults at 4242.