Cluster Upgrade

Kubernetes Cluster: Upgrade Package

The Kubernetes Cluster package is updated regularly with newer versions, components, and tools. Existing Kubernetes environments do not need to be recreated from scratch—the cluster can be upgraded through the built-in Kubernetes Cluster Configuration add-on.
On this page

Upgrade Overview

The platform provides an automated Kubernetes cluster upgrade process. Instead of replacing the entire environment, the upgrade add-on updates the existing cluster to the next available Kubernetes Cluster package version.

The upgrade mechanism is sequential: the platform upgrades the cluster to the next available version. If multiple newer releases exist, additional upgrade runs may be required to reach the newest package version.

Open the Upgrade Add-On

1Locate the Master layer

Open the Kubernetes environment in the platform dashboard and hover over the Master layer.

2Open Add-Ons

Click the Add-Ons button that appears for the Master layer.

3Select Upgrade

Find the Kubernetes Cluster Configuration add-on and choose the Upgrade option.

Start the Upgrade

1Confirm the operation

Confirm the upgrade request in the pop-up window.

2Allow the platform to update the cluster

The platform automatically upgrades the Kubernetes Cluster package to the next available version.

Before production upgrades: Review the Kubernetes Versions change log for component changes and verify compatibility of custom workloads, ingress resources, operators, CRDs, storage classes, and external integrations.

When the Latest Version Is Installed

If the cluster already uses the latest available Kubernetes Cluster package version, the platform displays an information notification instead of starting another upgrade.

Kubernetes cluster latest version notification
The dashboard notifies you when no newer Kubernetes Cluster package version is available.

Check Available Versions

Before or after an upgrade, review the Kubernetes Cluster Versions documentation to see available releases and their change logs.

  • Check which Kubernetes versions were added for new installations.
  • Review changes to bundled components such as ingress, dashboard, Helm, container runtime, CNI, and monitoring tools.
  • Identify known compatibility changes before upgrading production workloads.
Upgrade summary: Use the Kubernetes Cluster Configuration add-on on the Master layer, select Upgrade, confirm the operation, and allow the platform to move the existing environment to the next available package version.

What’s next?