Kubernetes minor-version upgrade

Keeping your Kubernetes cluster up to date ensures security and stability whilst enabling you to unlock cutting-edge capabilities, better performance, and long-term support.

With just a few clicks, you can seamlessly upgrade to the latest minor version.

Before starting the minor version upgrade, make sure that your cluster meets the following requirements:

• The cluster has active status
• There are no pending nodes (in cart, ordered or being created)
• The current Kubernetes version is 1.27 or higher
• The servers.com SSH keys on worker nodes haven't been deleted

It is only possible to upgrade to one version higher than your existing Kubernetes version. For example, if you have version 1.27, you can only upgrade to version 1.28.

See the list below for available upgrade options:

• 1.27 → 1.28
• 1.28 → 1.29
• 1.29 → 1.30
• 1.31 → 1.32

Upgrading from version 1.30 to 1.31 is temporarily unavailable to avoid service interruption. Contact our support team to discuss alternative upgrade variants.

Note that clusters are non-operational during the upgrade process and this process can't be suspended.

Upgrade management

To initiate the upgrade process, select a Kubernetes cluster and navigate to Kubernetes cluster details. If there is a new version available for the cluster you will see the Upgrade button near the Version field.

Upgrade process

Once an upgrade is initiated, it goes through the following steps:

• Verification of version compatibility (you’ll be informed if there are any issues).
• The cluster being upgraded will be issued Upgrading status and the upgrade will start in the control plane.
• Worker nodes will be upgraded in a groups of 10. Each worker node will be issued Upgrading status and will only return to Active status once the process is fully complete.
• Once the last node has been upgraded, the cluster version will be changed to the new one.

Suggested Articles