Supported versions
When creating a cluster, you select the Kubernetes version; the latest version is recommended in each case. centron automatically installs patch versions within your upgrade window; changing the minor version remains a deliberate decision. This page lists the available versions and explains how upgrades work.
Available versions
When creating a cluster, select the Kubernetes version in the Select a version section. The following versions are currently available:
| Version | Status |
|---|---|
| 1.33.1 | Recommended |
| 1.32.4 | Available |
Unless there are specific reasons within your team not to do so, we recommend using the latest version. An older version is advisable if you rely on tools or operators that have not yet been released for the latest version.
The list of versions changes with each new Kubernetes release. The selection in the creation dialogue is always the decisive factor; the version marked as recommended there is the recommended one.
Versioning scheme
Kubernetes uses the MAJOR.MINOR.PATCH schema; for example, 1.33.1:
- MAJOR (
1) – Major release. - MINOR (
33) – Feature release. New features, occasional changes to APIs. A change to the minor version is a deliberate step and is not carried out automatically. - PATCH (
1) – Bug fixes and security updates within a minor version, without any functional changes.
Automatic patch upgrades
In the Settings tab, under Automatically upgrade minor version patches, you can specify how new patch versions should be handled:
- Enabled – New patch versions are installed automatically.
- Disabled – Only essential upgrades are installed automatically.
Regardless of this setting, centron installs security-critical updates. Installation always takes place within your upgrade window – a four-hour period for which you specify the day of the week and start time.
For details on the procedure and configuration, please see Cluster-Upgrade.
Version changes and compatibility
Before changing the minor version, please check:
- Whether the API versions used by your manifests are still available in the target version.
- Whether your
kubectlversion matches the target version.kubectlsupports a deviation of one minor version either above or below the cluster version. - Whether operators, ingress controllers and Helm charts support the target version.
You can see the installed version of your cluster in the header of the cluster details view, next to ‘Project’ and ‘Region’.