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

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

<VersionMatrix />

> [!NOTE]
> A single Kubernetes patch version can be shipped by more than one Cluster Stack release. A newer release often adds fixes or cluster components without bumping Kubernetes itself (for example, several `1-32` releases all ship `v1.32.13`).

## 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 a Kubernetes version](/docs/hetzner/apalla/clusters/upgrades/update-within-a-version): move to a newer Cluster Stack release while staying on the same Kubernetes minor version.
- [Upgrade to a new Kubernetes version](/docs/hetzner/apalla/clusters/upgrades/upgrade-to-a-new-kubernetes-version): move to the next Kubernetes minor version along a tested upgrade path.

> [!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. Syself Autopilot will then lay out the precise sequence of releases to upgrade through.