Skip to content

feat(clickhouse): enable encryption#62

Open
MoisesGSalas wants to merge 1 commit intomainfrom
mgs/enable-encryption
Open

feat(clickhouse): enable encryption#62
MoisesGSalas wants to merge 1 commit intomainfrom
mgs/enable-encryption

Conversation

@MoisesGSalas
Copy link
Member

@MoisesGSalas MoisesGSalas commented Sep 22, 2025

This adds extra options to configure the clickhouse server with disk encryption and TLS support.

  1. To enable encryption you must set CLICKHOUSE_ENABLE_ENCRYPTION=true and provide a CLICKHOUSE_ENCRYPTION_KEY with at least 16 bytes (depending on the algorithm used).
  2. The playbook will copy the certificate and key located at CLICKHOUSE_CERTIFICATES_SOURCE_DIR (by default /tmp/clickhouse-certificates/ in the provisioning machine (the one running the playbook) to the target machine. The certificate and key must be named tls.crt and tls.key respectively.
  3. It's possible to define volume and mount configuration for the pod that runs each playbook independently. The idea is to mount k8s secret that holds the tls.crt and tls.key files.

Some additional configuration files were relocated.

Backup configuration was added.

@MoisesGSalas MoisesGSalas force-pushed the mgs/enable-encryption branch 10 times, most recently from 2bf43d4 to b579b67 Compare September 26, 2025 20:12
@MoisesGSalas MoisesGSalas marked this pull request as ready for review September 30, 2025 14:06
@MoisesGSalas MoisesGSalas requested a review from a team as a code owner September 30, 2025 14:06
@MoisesGSalas MoisesGSalas force-pushed the mgs/enable-encryption branch from b579b67 to 52ec2f3 Compare October 1, 2025 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant