Upgrading the cluster from Kubernetes 1.36
Plan Your Next Upgrade
You are seeing the documentation for Kubernetes 1.36 — the newest Kubernetes minor Syself Autopilot supports right now.
If your cluster is already on this version, there's nothing to do.
Not on this version? Documentation is tailored to each Cluster Stack release. Pick your cluster's actual version to jump straight to the guide that applies to it:
Not sure which Kubernetes version your cluster is on?
If you're not sure which Kubernetes version your cluster is currently on, check it directly:
Check in your cluster
Run these commands against the Syself Autopilot management cluster, not the workload cluster.
To check one cluster:
$ kubectl get cluster <cluster-name> -n <namespace> \
-o jsonpath='{.spec.topology.classRef.name}{"\n"}'
The command returns the Cluster Stack release name:
hetzner-apalla-1-36-v6
The name includes the provider, stack, Kubernetes minor version, and Cluster Stack release. The final vN segment identifies the Cluster Stack release.
To check every cluster:
$ kubectl get clusters -A \
-o custom-columns='NAMESPACE:.metadata.namespace,CLUSTER:.metadata.name,CLUSTERSTACK:.spec.topology.classRef.name,KUBERNETES:.spec.topology.version'
If the management cluster serves cluster.x-k8s.io/v1beta1:
If the Syself Autopilot management cluster serves cluster.x-k8s.io/v1beta1 instead of v1beta2, use spec.topology.class instead of spec.topology.classRef.name.
To check one cluster with cluster.x-k8s.io/v1beta1:
$ kubectl get cluster <cluster-name> -n <namespace> \
-o jsonpath='{.spec.topology.class}{"\n"}'
To check every cluster with cluster.x-k8s.io/v1beta1:
$ kubectl get clusters -A \
-o custom-columns='NAMESPACE:.metadata.namespace,CLUSTER:.metadata.name,CLUSTERSTACK:.spec.topology.class,KUBERNETES:.spec.topology.version'
Match the docs to your version
If it doesn't show 1.36, switch the docs to your cluster's actual version using the picker below:
An upgrade guide scoped to that version will walk you through the upgrade path to get here.
Explore further
Exactly which components and versions hetzner-apalla-1-36-v6 ships.
Plan Your Next Upgrades
The new Version Hub is here. Check the independent support cycles for Kubernetes 1.33 to 1.36 before provisioning or upgrading your clusters.
Open Version HubNote
Starting from hetzner-apalla-1-35-v1, Hetzner node image builds are no longer required. Because of that, we require a common SSH key for both bare metal and cloud servers. If you did not use the same SSH key when doing the Hetzner account preparation , please change the secrets to ensure you have a single SSH key.