ClickHouse Operator

The ClickHouse Operator is a Kubernetes operator that automates the deployment, configuration, and management of ClickHouse and ClickHouse Keeper clusters.

  • Databases
  • Infrastructure
  • Tools & Utilities
The ClickHouse Operator is a Kubernetes operator that automates the deployment, configuration, and management of ClickHouse and ClickHouse Keeper clusters. It provides declarative cluster management through custom resources, handling scaling, upgrades, and configuration so homelabbers and platform teams can run highly-available ClickHouse deployments without manual intervention.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

66/100 Good

Maintained
100last commit 18 days ago
Popular
50313 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1016 GB minimum RAM
Security check
94no serious findings, 1 minor, CI, tests

Availability: platform listings confirmed today

GitHub stars
313
Open issues
16
Last commit
2026-11-03
Latest release
v0.0.8
License
Apache-2.0
Activity
declining

Checked 18 days ago - source: GitHub (clickhouse/clickhouse-operator)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 4 CPU core(s), 1024 GB disk.

Checked 23 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Extract and start the ClickHouse server Unpack the clickhouse-server package, run its install script's configure step, then start the service. If the server is not running, the operator cannot manage ClickHouse and connections will fail. source
  • Check the container says Started After `docker compose up --detach`, wait for the output to show the container Started before you connect to it. This confirms the service is actually up and ready. source
  • Leave port 9181 open for Keeper ClickHouse Keeper listens on port 9181, so management tools must be able to reach it. If that port is blocked, commands time out or cannot find the service. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does ClickHouse Operator also deploy and manage ClickHouse Keeper clusters?

Yes. It automates the deployment, configuration, and management of ClickHouse clusters and ClickHouse Keeper clusters on Kubernetes.

What users.xml access management setting is asked about when deploying the ClickHouse Operator?

A Stack Overflow question asks how to enable or uncomment access_management in users.xml when deploying the ClickHouse Kubernetes operator.

Where are open ClickHouse Operator issues listed?

The official repository has a GitHub issues area for tracking and discussing project issues.

Answers sourced from clickhouse.com, github.com, stackoverflow.com

Community

Collected 48 days ago - public community threads