Helm deployment options (v1.x)

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/use-cases/observability/clickstack/deployment/oss/helm/v1/helm-deployment-options-v1.md)

Deprecated — v1.x chart

This page documents deployment options for the **v1.x** inline-template Helm chart, which is in maintenance mode. For the v2.x chart, see [Helm deployment options](/docs/use-cases/observability/clickstack/deployment/helm-deployment-options). To migrate, see the [Upgrade guide](/docs/use-cases/observability/clickstack/deployment/helm-upgrade).

This guide covers advanced deployment options for ClickStack using Helm. For basic installation, see the [main Helm deployment guide](/docs/use-cases/observability/clickstack/deployment/helm-v1).

## Overview[​](#overview "Direct link to Overview")

ClickStack's Helm chart supports multiple deployment configurations:

- **Full stack** (default) - All components included
- **External ClickHouse** - Use existing ClickHouse cluster
- **External OTEL Collector** - Use existing OTEL infrastructure
- **Minimal deployment** - Only HyperDX, external dependencies

## External ClickHouse[​](#external-clickhouse "Direct link to External ClickHouse")

If you have an existing ClickHouse cluster (including ClickHouse Cloud), you can disable the built-in ClickHouse and connect to your external instance.

### Option 1: Inline configuration (development/testing)[​](#external-clickhouse-inline "Direct link to Option 1: Inline configuration (development/testing)")

Use this approach for quick testing or non-production environments:

```
# values-external-clickhouse.yaml
clickhouse:
  enabled: false  # Disable the built-in ClickHouse

otel:
  clickhouseEndpoint: "tcp://your-clickhouse-server:9000"
  clickhousePrometheusEndpoint: "http://your-clickhouse-server:9363"  # Optional

hyperdx:
  defaultConnections: |
    [
      {
        "name": "External ClickHouse",
        "host": "http://your-clickhouse-server:8123",
        "port": 8123,
        "username": "your-username",
        "password": "your-password"
      }
    ]
```

Install with this configuration:

```
helm install my-clickstack clickstack/clickstack -f values-external-clickhouse.yaml
```

### Option 2: External secret (production recommended)[​](#external-clickhouse-secret "Direct link to Option 2: External secret (production recommended)")

For production deployments where you want to keep credentials separate from your Helm configuration:

### Using ClickHouse Cloud[​](#using-clickhouse-cloud "Direct link to Using ClickHouse Cloud")

For ClickHouse Cloud specifically:

```
# values-clickhouse-cloud.yaml
clickhouse:
  enabled: false
  persistence:
    enabled: false

otel:
  clickhouseEndpoint: "tcp://your-cloud-instance.clickhouse.cloud:9440?secure=true"

hyperdx:
  useExistingConfigSecret: true
  existingConfigSecret: "clickhouse-cloud-config"
  existingConfigConnectionsKey: "connections.json"
  existingConfigSourcesKey: "sources.json"
```

## External OTEL Collector[​](#external-otel-collector "Direct link to External OTEL Collector")

If you have an existing OTEL collector infrastructure:

```
# values-external-otel.yaml
otel:
  enabled: false  # Disable the built-in OTEL collector

hyperdx:
  otelExporterEndpoint: "http://your-otel-collector:4318"
```

```
helm install my-clickstack clickstack/clickstack -f values-external-otel.yaml
```

For instructions on exposing OTEL collector endpoints via ingress, see [Ingress Configuration](/docs/use-cases/observability/clickstack/deployment/helm-configuration-v1#otel-collector-ingress).

## Minimal deployment[​](#minimal-deployment "Direct link to Minimal deployment")

For organizations with existing infrastructure, deploy only HyperDX:

```
# values-minimal.yaml
clickhouse:
  enabled: false

otel:
  enabled: false

hyperdx:
  otelExporterEndpoint: "http://your-otel-collector:4318"

  # Option 1: Inline (for testing)
  defaultConnections: |
    [
      {
        "name": "External ClickHouse",
        "host": "http://your-clickhouse-server:8123",
        "port": 8123,
        "username": "your-username",
        "password": "your-password"
      }
    ]

  # Option 2: External secret (production)
  # useExistingConfigSecret: true
  # existingConfigSecret: "my-external-config"
  # existingConfigConnectionsKey: "connections.json"
  # existingConfigSourcesKey: "sources.json"
```

```
helm install my-clickstack clickstack/clickstack -f values-minimal.yaml
```

## Next steps[​](#next-steps "Direct link to Next steps")

- [Configuration Guide (v1.x)](/docs/use-cases/observability/clickstack/deployment/helm-configuration-v1) - API keys, secrets, and ingress setup
- [Cloud Deployments (v1.x)](/docs/use-cases/observability/clickstack/deployment/helm-cloud-v1) - GKE, EKS, and AKS specific configurations
- [Main Helm Guide (v1.x)](/docs/use-cases/observability/clickstack/deployment/helm-v1) - Basic installation
- [Deployment options (v2.x)](/docs/use-cases/observability/clickstack/deployment/helm-deployment-options) - v2.x deployment options
- [Upgrade guide](/docs/use-cases/observability/clickstack/deployment/helm-upgrade) - Migrating from v1.x to v2.x

- [Overview](#overview)- [External ClickHouse](#external-clickhouse)
    - [Option 1: Inline configuration (development/testing)](#external-clickhouse-inline)- [Option 2: External secret (production recommended)](#external-clickhouse-secret)- [Using ClickHouse Cloud](#using-clickhouse-cloud)- [External OTEL Collector](#external-otel-collector)- [Minimal deployment](#minimal-deployment)- [Next steps](#next-steps)

Was this page helpful?