feat!: use ClickHouse operator and OSS-licensed subcharts (v2.0.0)

[Steffen911]

Summary

• Deploy ClickHouse via the clickhouse-operator (chart oci://ghcr.io/clickhouse/clickhouse-operator-helm v0.0.4), with new templates for ClickHouseInstallation and ClickHouseKeeperInstallation plus an auth secret.
• Replace Bitnami subcharts with OSS-licensed alternatives: groundhog2k/postgres, valkey-io/valkey, and seaweedfs.
• Add Helm-managed secrets for Postgres, Redis (Valkey), S3 (SeaweedFS), and ClickHouse so credentials are templated consistently across in-cluster and external backends.
• Bump chart to 2.0.0 (breaking — values schema and dependency set both changed).
• Update examples/minimal-installation and chart unit tests to match the new value shape.

Refs: LFE-9679

Test plan

• helm dependency update charts/langfuse resolves cleanly (verified locally)
• helm lint charts/langfuse passes
• helm unittest charts/langfuse passes
• helm template charts/langfuse -f examples/minimal-installation/values.yaml renders without errors
• End-to-end install in a kind/minikube cluster: web + worker reach ready, ClickHouse cluster + keeper come up, ingestion + read paths work
• Verify cert-manager prereq is documented for users (clickhouse-operator webhook depends on it)

🤖 Generated with Claude Code

[github-actions]

Helm Unit Test Results

60 tests   - 1   60 ✅  - 1   0s ⏱️ -3s
10 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit af97e1b. ± Comparison against base commit 9795e03.

This pull request removes 7 and adds 6 tests. Note that renamed tests count towards both.

test clickhouse cluster configuration ‑ should NOT set CLICKHOUSE_CLUSTER_ENABLED when clusterEnabled is true (default) with external ClickHouse
test clickhouse cluster configuration ‑ should NOT set CLICKHOUSE_CLUSTER_ENABLED when deploying multi-replica ClickHouse cluster
test clickhouse cluster configuration ‑ should respect default clusterEnabled=true with multi-replica deployment
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to false when clusterEnabled is explicitly false with external ClickHouse
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to false when clusterEnabled is false even with multi-replica deployment
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to false when deploying single replica ClickHouse
test s3 media upload validation ‑ should fail when MinIO deployed without forcePathStyle and media upload enabled

test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to false when cluster.enabled is explicitly false with external ClickHouse
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to false when cluster.enabled is false even with multi-replica deployment
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to true when cluster.enabled is true (default) with external ClickHouse
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to true when deploying multi-replica ClickHouse cluster
test clickhouse cluster configuration ‑ should set CLICKHOUSE_CLUSTER_ENABLED to true when deploying single-replica ClickHouse (operator-managed cluster)
test s3 media upload validation ‑ should fail when bundled S3 deployed without forcePathStyle and media upload enabled

♻️ This comment has been updated with latest results.

[davidrubio-dp]

Hello! Are there any expectations about when is this new version of the chart going to be available? Thanks

[chrisjaimon2012]

@Steffen911 which operator will you be going with? Altinity? or the official operator?

[Steffen911]

@chrisjaimon2012 We'll go with the official clickhouse operator.