Updating the cluster from hetzner-apalla-1-36-v6
Plan Your Next Update
You are seeing the documentation for Kubernetes 1.36, Cluster Stack release hetzner-apalla-1-36-v6 — the newest release Syself Autopilot offers right now.
If your cluster is already on this release, there's nothing to do.
Not on this release? 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 Cluster Stack release your cluster is on?
If you are unsure which Cluster Stack release your cluster is currently running, do the following:
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 either one doesn't match hetzner-apalla-1-36-v6 / 1.36, switch the docs to your cluster's actual version using the picker below:
An update guide scoped to that version will show you the real update steps.
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 HubPlan maintenance and run prechecks
What to check before upgrading a Syself Autopilot cluster: pod disruption budgets, control plane health, node capacity, and pending CSRs.
Upgrade Kubernetes version
Move a running cluster to a new Kubernetes minor version — edit the cluster object, let the nodes roll, and confirm the upgrade finished.