Altinity Kubernetes Operator for ClickHouse creates, configures and manages ClickHouse clusters running on Kubernetes
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.4...release-0.23.5
NOTE: There was a lot of internal refactoring related to Keeper code, but no functional changes yet. The Keeper configuration functionality will be improved in the next major release.
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.3...release-0.23.4
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.2...release-0.23.3
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.1...release-0.23.2
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.0...release-0.23.1
users:
user1/password:
valueFrom:
secretKeyRef:
name: clickhouse_secret
key: pwduser1
settings:
s3/my_bucket/access_key:
valueFrom:
secretKeyRef:
name: s3-credentials
key: AWS_ACCESS_KEY_ID
files:
server.key:
valueFrom:
secretKeyRef:
name: clickhouse-certs
key: server.key
See updated Security Hardening Guide for more detail.
kind: ClickHouseKeeperInstallation
See examples in there: https://github.com/Altinity/clickhouse-operator/tree/0.23.0/docs/chk-examples The implementation is not final, following things yet needs to be done:
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.2...release-0.23.0
files/settings.xml
.Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.1...release-0.22.2
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.0...release-0.22.1
spec:
reconcile:
host:
wait:
queries: "false"
In CHI:
spec:
reconciling:
policy: nowait
reconcile:
# Reconcile runtime settings
runtime:
# Max number of concurrent CHI reconciles in progress
reconcileCHIsThreadsNumber: 10
# The operator reconciles shards concurrently in each CHI with the following limitations:
# 1. Number of shards being reconciled (and thus having hosts down) in each CHI concurrently
# can not be greater than 'reconcileShardsThreadsNumber'.
# 2. Percentage of shards being reconciled (and thus having hosts down) in each CHI concurrently
# can not be greater than 'reconcileShardsMaxConcurrencyPercent'.
# 3. The first shard is always reconciled alone. Concurrency starts from the second shard and onward.
# Thus limiting number of shards being reconciled (and thus having hosts down) in each CHI by both number and percentage
# Max number of concurrent shard reconciles within one CHI in progress
reconcileShardsThreadsNumber: 5
# Max percentage of concurrent shard reconciles within one CHI in progress
reconcileShardsMaxConcurrencyPercent: 50
clickhouse_operator_chi_reconciles_started
clickhouse_operator_chi_reconciles_completed
clickhouse_operator_chi_reconciles_timings
clickhouse_operator_host_reconciles_started
clickhouse_operator_host_reconciles_completed
clickhouse_operator_host_reconciles_restarts
clickhouse_operator_host_reconciles_errors
clickhouse_operator_host_reconciles_timings
clickhouse_operator_pod_add_events
clickhouse_operator_pod_update_events
clickhouse_operator_pod_delete_events
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.21.3...release-0.22.0
Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.21.2...release-0.21.3