CLICKHOUSE // DATABASES
ClickHouse on Your Cluster
Provision distributed ClickHouse analytics clusters on your own cluster, coordinated by ClickHouse Keeper. Sharding, replication, optional TLS, and query insights — running on your infrastructure.
Powered by ClickHouse Operator
Available versions
FEATURES // CLICKHOUSE
Analytics at Scale
Edka provisions ClickHouse on your own cluster and gives you a clean control surface for day-2 operations. The data stays in your cloud account.
Distributed Topology
Shard and replicate for scale and resilience.
- Server replicas per shard and shard count
- ClickHouse Keeper quorum of 1, 3, or 5
- Node-pool placement and taint tolerations
Storage & Resources
Size ClickHouse and Keeper independently.
- Dedicated ClickHouse and Keeper storage
- Independent CPU and memory for ClickHouse and Keeper pods
Security & TLS
Encrypt and expose on your terms.
- Optional internal TLS via cert-manager
- Default user password
- Public LoadBalancer (TLS required), MetalLB, or Tailscale exposure
Analytics Insights
See how queries and the runtime perform.
- Runtime metrics
- ClickHouse query workload insights
Runs on Your Cluster
Your analytics, your infrastructure.
- ClickHouse operator and Keeper run in your cluster
- Requires Kubernetes v1.33 or later
- You keep full control — no hosted database service
Other engines
PostgreSQL 
MySQL 
Valkey GET STARTED // NOW
Provision ClickHouse
Spin up a distributed ClickHouse analytics cluster with Keeper coordination — on your own infrastructure.
Which ClickHouse versions can I deploy with Edka?
Available versions today: 26.4, 25.12. You pick the version when provisioning the runtime.
How does Edka run distributed ClickHouse?
You set server replicas per shard and the shard count, coordinated by a ClickHouse Keeper quorum of 1, 3, or 5. The Altinity ClickHouse Operator runs in your cluster and requires Kubernetes v1.33 or later.
Can ClickHouse connections be encrypted?
Yes. Internal TLS is available via cert-manager. Public LoadBalancer exposure requires TLS; private MetalLB and Tailscale exposure are also supported.
Where does my ClickHouse data live?
In your own Kubernetes cluster, on your own infrastructure. There is no hosted database service in between. You keep full control of the runtime and its storage.