fix(clickhouse): load profile settings via users.d in customConfig

[NitinKumar004]

Problem

customConfig in the ClickHouse chart was mounted only into /etc/clickhouse-server/config.d/. ClickHouse reads server-level settings from config.d, but profile/user settings are read only from the users config tree (users.d). So a <profiles> block placed in customConfig was silently ignored — no error, no warning, just no effect.

Observed live on the zopnight release: max_server_memory_usage_to_ram_ratio (server-level) applied correctly, but max_memory_usage, max_bytes_before_external_group_by, and max_bytes_before_external_sort (profile-level) never loaded (changed=0, default profile empty). This contributed to ClickHouse OOMs (code 241) on heavy aggregation queries, since the intended per-query cap and spill-to-disk thresholds were never in effect.

This is standard ClickHouse behavior on the official image (not a Bitnami/chart quirk) — config.d and users.d are separate trees read by different parts of the server.

Fix

Mount the same customConfig document into both trees:

• /etc/clickhouse-server/config.d/custom.xml — server-level settings
• /etc/clickhouse-server/users.d/custom.xml — profile/user settings

ClickHouse reads the relevant sections from each tree and ignores the rest, so a single document can carry both. No change to deploy values is required — existing customConfig blobs start working after a helm upgrade.

Verification (minikube, official clickhouse/clickhouse-server:25.3)

• Render: empty customConfig → no ConfigMap/mounts; server-only / profiles-only / mixed → both mounts render.
• Live deploy of the real mixed config:
  • Pod Running 1/1, 0 restarts; no config-related errors/warnings in logs.
  • Server setting max_server_memory_usage_to_ram_ratio=0.9 → changed=1.
  • Profile settings max_memory_usage=1.5G, max_bytes_before_external_group_by=750M, max_bytes_before_external_sort=750M → all changed=1; default profile populated; enforced via getSetting().
  • Non-default users: created aggregator_tpbh exactly as the chart does (SQL CREATE USER, no settings profile) and confirmed it inherits all three limits via the server default_profile.

Changes

• templates/statefulset.yaml — add users.d/custom.xml mount of the existing custom-config ConfigMap.
• values.yaml — document both mount paths in the customConfig comment.
• README.md — document dual-mount behavior with example.

🤖 Generated with Claude Code

[arunesh-j]

Update to a newer version and package it ..

[NitinKumar004]

Done @arunesh-j — bumped the chart to v0.0.3 and packaged it the same way as the last release (#289):

• charts/clickhouse/Chart.yaml: 0.0.2 → 0.0.3
• packaged docs/clickhouse-v0.0.3.tgz (helm package --version v0.0.3)
• regenerated docs/index.yaml (merged, older v0.0.2/v0.0.1 entries retained)

helm lint passes. Pushed in c2f46ee.

dismiss