> ## Documentation Index
> Fetch the complete documentation index at: https://private-7c7dfe99-trino-dialect.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Component Versions

Current stable versions for all ClickHouse Private components. Use these tags when copying artifacts to your registry and installing via Helm.

## Release channel

ClickHouse Private follows the **slow** (deferred) release channel of ClickHouse Cloud, the most conservative of the Cloud channels, intended for risk-averse deployments. A ClickHouse version only becomes a candidate for a ClickHouse Private release once it has started rolling out to the slow channel in Cloud, which is roughly four weeks after the same version starts rolling out to the fast channel.

Reaching the slow channel does not release a version for ClickHouse Private. ClickHouse Private sits at the conservative end of the slow channel: every version goes through our own validation before it is released, so it lands after the Cloud slow rollout has begun.

The [ClickHouse Cloud release status page](https://clickhouse.com/docs/resources/changelogs/cloud/release-status) 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](/cloud/clickhouse-private/reference/changelog) are authoritative for what ClickHouse Private actually ships.

## Container Images

| Component                  | Image Tag             | Description                                              |
| -------------------------- | --------------------- | -------------------------------------------------------- |
| clickhouse-server          | `26.2.1.525`          | ClickHouse server (standard)                             |
| clickhouse-server (FIPS)   | `26.2.1.525-fips`     | ClickHouse server with FIPS 140-3 compliance             |
| clickhouse-keeper          | `26.2.1.258`          | Distributed coordination service (ZooKeeper alternative) |
| clickhouse-keeper (FIPS)   | `26.2.1.258-fips`     | ClickHouse keeper with FIPS 140-3 compliance             |
| clickhouse-operator        | `main-1.20441.1`      | Kubernetes operator for cluster lifecycle management     |
| clickhouse-operator (FIPS) | `main-1.20441.1-fips` | ClickHouse operator with FIPS 140-3 compliance           |

## Helm Charts

| Chart                          | Version     | Description                                  |
| ------------------------------ | ----------- | -------------------------------------------- |
| helm/clickhouse-operator-helm  | `1.20441.1` | Installs the ClickHouse operator             |
| helm/onprem-clickhouse-cluster | `1.8.7`     | Creates a ClickHouseCluster custom resource  |
| helm/airgap-management         | `1.173.2`   | Optional management API                      |
| helm/preflight-check           | `1.38.4`    | Pre-installation validation checks           |
| helm/support-bundle            | `1.11.3`    | Collects diagnostic data for troubleshooting |

## API

| Component         | Version   |
| ----------------- | --------- |
| airgap-management | `1.173.2` |

## Notes

* The **operator Helm chart version** (`1.20441.1`) differs from the operator **image tag** (`main-1.20441.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.