# ClusterStack releases and Kubernetes versions

Every ClusterStack release ships a specific patch version of Kubernetes. The table below maps each `hetzner-apalla` ClusterStack release to the Kubernetes version it provides, together with its release date — so you can see at a glance which release corresponds to which Kubernetes version.

By default the table shows the **latest** ClusterStack release for each Kubernetes minor version. Choose **Show all releases** to expand the full history.

{% versionmatrix /%}

{% callout type="note" %}

A single Kubernetes patch version can be shipped by more than one ClusterStack release — a newer release often adds fixes or addons without bumping Kubernetes itself (for example, several `1-32` releases all ship `v1.32.13`).

{% /callout %}

## Planning an upgrade

Upgrades follow **tested upgrade paths**, and you cannot skip more than one Kubernetes minor version at a time. To upgrade your cluster step by step, see:

- [Update within the same Kubernetes version](/docs/hetzner/apalla/how-to-guides/update-clusters/update-cluster-with-same-kubernetes-version) — move to a newer ClusterStack release while staying on the same Kubernetes minor version.
- [Update to a new Kubernetes version](/docs/hetzner/apalla/how-to-guides/update-clusters/update-cluster-to-a-new-kubernetes-version) — move to the next Kubernetes minor version along a tested upgrade path.

{% callout type="tip" %}

For the guided, step-by-step path from the exact version your cluster is on, open the **version selector** at the top of the navigation and select your current version. Autopilot will then lay out the precise sequence of releases to upgrade through.

{% /callout %}