// the find
Altinity/clickhouse-operator
Altinity Kubernetes Operator for ClickHouse creates, configures and manages ClickHouse® clusters running on Kubernetes
A Kubernetes operator for ClickHouse that handles cluster provisioning, scaling, configuration management, and version upgrades via CRDs. Backed by Altinity, the primary commercial ClickHouse support company, which means it's actually maintained. Aimed at teams running ClickHouse on Kubernetes who want declarative cluster management instead of hand-managing StatefulSets.
Active development with recent commits and a real company behind it — not an abandoned side project. Ships a dedicated ClickHouseKeeper operator (CHK) alongside the main CHI operator, so you're not forced to run Zookeeper just for replication coordination. FIPS 140-3 compatible builds with GOFIPS140 enforcement baked in — rare for this class of tool and meaningful if you're in a regulated environment. Prometheus metrics exporter is a separate binary, not bolted onto the operator, which makes the monitoring surface independently deployable.
Schema migrations are still on you — the operator handles cluster topology but doesn't know anything about your ClickHouse table schemas, so rolling out DDL changes across a scaled cluster is your problem. The CHI CRD is genuinely complex; the 'max' example YAML runs to hundreds of lines, and there's no validation feedback when you misconfigure something subtle like shard/replica topology. Zookeeper setup documentation still exists alongside ClickHouse Keeper docs, which creates confusion about which coordination layer you should actually be using in 2026. No built-in support for ClickHouse Cloud or hybrid topologies — this is purely self-managed Kubernetes.