ClickStack Helm Charts

ClickStack is an open-source observability stack combining ClickHouse, HyperDX, and OpenTelemetry for logs, metrics, and traces.

Quick Start

helm repo add clickstack https://clickhouse.github.io/ClickStack-helm-charts
helm repo update

# Step 1: Install operators and CRDs
helm install clickstack-operators clickstack/clickstack-operators

# Step 2: Install ClickStack (after operators are ready)
helm install my-clickstack clickstack/clickstack

For configuration, cloud deployment, ingress setup, and troubleshooting, see the official documentation.

Charts

• clickstack/clickstack-operators - Installs the MongoDB and ClickHouse operator controllers and CRDs. Must be installed first.
• clickstack/clickstack - Installs HyperDX, OpenTelemetry Collector, and operator custom resources.

Additional Manifests

The clickstack chart supports deploying arbitrary Kubernetes objects (NetworkPolicy, HPA, ServiceAccount, PodMonitor, ALB Ingress, etc.) alongside the chart's own resources via the additionalManifests value. See the Additional Manifests Guide for values-file constraints and examples, including AWS ALB example values.

Production Hardening

Chart defaults are safe for development (Service ClusterIP, Ingress disabled). For production deployments — and especially for any deployment that exposes the OTLP gRPC receiver or fronts HyperDX with an HTTP/2-capable Ingress — see docs/SECURITY-HARDENING.md. Covers ingress controller version pinning (HTTP/2 bomb mitigation), NetworkPolicy examples, and recommended resource limits.

Operator Dependencies

The clickstack-operators chart bundles:

• MongoDB Kubernetes Operator (MCK) - Manages MongoDB Community replica sets via a MongoDBCommunity custom resource.
• ClickHouse Operator - Manages ClickHouse and Keeper clusters via ClickHouseCluster and KeeperCluster custom resources.

The clickstack chart includes:

• OpenTelemetry Collector - Deploys the ClickStack OTEL collector image via the official OpenTelemetry Collector Helm chart.

Uninstalling

Uninstall in reverse order:

helm uninstall my-clickstack            # Remove app + CRs first
helm uninstall clickstack-operators     # Remove operators + CRDs

Note: PersistentVolumeClaims created by the MongoDB and ClickHouse operators are not removed by helm uninstall. This is by design to prevent accidental data loss. To clean up PVCs, refer to:

• MongoDB Kubernetes Operator docs
• ClickHouse Operator cleanup docs

Upgrading

If you are upgrading from the inline-template chart (v1.x), see the Upgrade Guide for migration instructions.

Support

• Documentation - Installation, configuration, guides
• Issues - Report bugs or request features