Skip to main content
Current stable versions for all ClickHouse Private components. Use these tags when copying artifacts to your registry and installing via Helm.
Preserve the image tags provided by ClickHouse when copying images to your registry. Do not rename or replace them with different tags. Some ClickHouse Private components validate these tags and rely on their specific structure during air-gapped installations and upgrades.

Release channel

ClickHouse Private follows the regular release channel of ClickHouse Cloud, the channel Cloud recommends for production services. A ClickHouse version only becomes a candidate for a ClickHouse Private release once it has started rolling out to the regular channel in Cloud, which is roughly two weeks after the same version starts rolling out to the fast channel. Reaching the regular channel does not release a version for ClickHouse Private. ClickHouse Private sits at the conservative end of the regular channel: every version goes through our own validation before it is released, so it lands after the Cloud regular rollout has begun. ClickHouse Private moved to the regular channel with the 2026-11-13 release. Earlier releases followed the slow (deferred) channel. The ClickHouse Cloud release status page tracks where each ClickHouse version sits in that rollout, and is the best indicator of which versions are approaching a ClickHouse Private release. Note that its dates describe the Cloud rollout only, and no date on that page is a commitment for ClickHouse Private. The tables below and the Changelog are authoritative for what ClickHouse Private actually ships. For how long each major version is supported, see End-of-Life Dates.

Container Images

Helm Charts

API

Notes

  • The operator Helm chart version (1.23255.1) differs from the operator image tag (main-1.23255.1). Use the Helm chart version when installing via helm install and the image tag when copying container images.
  • The ClickHouse server and keeper tags are listed so you can mirror those images into your registry. You do not normally pass them to Helm: each onprem-clickhouse-cluster chart version pins the tested and validated pair for its release. FIPS is the exception, as below.
  • FIPS builds append -fips to the standard image tags for server, keeper, and operator. There is a single Helm chart per component — the FIPS variant is selected by the image tag, not by a different chart version.
Last modified on November 13, 2026