Skip to content

Platform Version

Overview

Platform versioning for Managed Kubernetes Service (MKS) clusters enables in-place upgrades of core components such as ETCD, CRI, and Salt-minion without affecting existing configurations or requiring full cluster upgrades. This feature was introduced to reduce the complexity and risk associated with Kubernetes upgrades by decoupling component updates from the Kubernetes version. It ensures consistent versions across nodes, improves cluster stability, addresses security vulnerabilities, and provides a more predictable, controlled, and reliable upgrade process with minimal disruption to cluster operations.

Did you know ?

Platform Versioning can be managed through various methods:

ℹ️ Note: Proceed with this Platform Version upgrade only after ensuring the cluster is healthy.

On New Clusters

When provisioning a new MKS cluster, the platform version defaults to the latest available version, which is currently v1.0.0.

EKS Architecture

On Existing Clusters

To upgrade the platform version of an existing cluster from v0.1.0 to v1.0.0:

  • Select the cluster and go to its Configuration page
  • Click Upgrade Available next to the Platform Version field

EKS Architecture

The Upgrade Platform Version screen appears, indicating that a new platform version upgrade is available from v0.1.0 to v1.0.0. This upgrade is required to ensure consistent lifecycle management of critical cluster components.

The following components will be upgraded: - Salt-Minion - CRI - ETCD

⚠️ Warning
Platform version upgrades are disruptive and require downtime, as core components such as ETCD and CRI will be upgraded.

  • Click Upgrade

EKS Architecture

Once the upgrade request is submitted, the status will be displayed as In Progress. When the upgrade is successful, the latest version will be shown below.

EKS Architecture

Upgrade Platform and K8s Versions Together

Upgrading the platform version along with the Kubernetes (K8s) version is possible.

Initiate Kubernetes Version Upgrade

From the Clusters dashboard, initiate the Kubernetes version upgrade using either of the following methods:

  • Click the gear icon on the required cluster card and select Upgrade K8s Version from the dropdown menu
  • Alternatively, click the Upgrade Available banner displayed on the cluster card

EKS Architecture

Clicking the Upgrade Available banner opens a side panel that allows to upgrade the Kubernetes version and the Platform Version (which includes CRI, ETCD, and Salt minion components).

EKS Architecture

Select the desired Kubernetes and Platform versions, then click Upgrade

⚠️ Important: Although it is possible to upgrade both the Kubernetes and Platform versions together, it is not recommended.

If the Platform version upgrade fails for any reason such as a disruption in network connectivity, issues with node communication, or problems during component updates, the entire upgrade process will fail, including the Kubernetes version upgrade.

Even if the Kubernetes upgrade is capable of completing successfully, it will not proceed because the workflow treats both upgrades as a single operation.

To avoid such failures and ensure a controlled rollout, it is strongly recommended to upgrade the Platform version first, verify its success, and then proceed with the Kubernetes upgrade.