How to check the Kubernetes version and Cluster Stack
Run these commands against the Syself Autopilot management cluster, not the workload cluster, to find which Kubernetes version and Cluster Stack release your cluster uses.
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-v2
The name includes the provider, stack, Kubernetes minor version, and Cluster Stack release. The final vN segment identifies the Cluster Stack release.
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:
$ kubectl get cluster <cluster-name> -n <namespace> \
-o jsonpath='{.spec.topology.class}{"\n"}'
To check every cluster:
$ kubectl get clusters -A \
-o custom-columns='NAMESPACE:.metadata.namespace,CLUSTER:.metadata.name,CLUSTERSTACK:.spec.topology.class,KUBERNETES:.spec.topology.version'
Use the version picker below to select the Kubernetes minor and Cluster Stack release that match the values for your cluster.
Documentation is tailored to each Cluster Stack release. Select the Kubernetes minor and release your cluster currently uses, rather than the latest version, to see the documentation that applies to your cluster.
Build an SCS-compatible cluster
How to create a Kubernetes cluster compatible with the Sovereign Cloud Stack guidelines.
Plan maintenance and run prechecks
What to check before upgrading a Syself Autopilot cluster: deprecated API usage, pod disruption budgets, control plane health, node capacity, and pending CSRs.