Kubernetes version support policy

Kubernetes (K8s) is an open source project that is constantly evolving, integrating and deprecating features and applying bug fixes. The project is supported by the community, which releases between four and six new minor versions every year.

With Scaleway Kubernetes, you can use the latest version of Kubernetes as soon as it is officially released and certified by the Cloud Native Computing Foundation. The versions are usually available in Kubernetes Kapsule and Kubernetes Kosmos within a few days after the release.

Version management recommendation

We recommend that you keep your Kubernetes clusters up-to-date with the latest available minor version of Kubernetes and the latest patches.

Cluster auto-upgrade

Before using the auto-upgrade feature, it is essential to differentiate between patch upgrades and minor version upgrades in Kubernetes. While a patch upgrade typically focuses on bug fixes and security patches without altering existing functionalities, a minor version upgrade introduces new features and changes.

The Kubernetes Kapsule and Kubernetes Kosmos platforms offer an auto-upgrade feature to address patch upgrades within the same minor Kubernetes version you are currently using. This means that the feature allows for updates to the latest patch, ensuring enhanced security and stability without introducing major changes.

This upgrade applies to both the control plane and the managed node versions of Kubernetes. You can activate this feature through the API, CLI, or the Scaleway console. Note, to ensure smooth operation of the auto-upgrade, the kube-system namespace should remain untouched and free from any user-initiated modifications that might cause issues with the upgrade process.

If you are looking to upgrade to the next minor version of Kubernetes, refer to our documentation on upgrading to the next minor version.

Support

Before opening a support ticket related to cluster behavior or a Kubernetes component, we highly recommend that you upgrade the cluster to the latest version of Kubernetes. If the upgrade to a new minor version is not possible, the latest patch of the version running on the cluster must be applied.

80% of Kubernetes issues are usually fixed when applying the latest patch version available.

Scaleway Kubernetes Kapsule & Kosmos release calendar

• Official End of Life: Upstream end of maintenance support.
• Scaleway Release: Version is available for Kubernetes Kapsule and Kubernetes Kosmos cluster creation and cluster upgrade.
• Deprecation: Version is removed from cluster creation option. Customers are informed via a support ticket that they are using a deprecated version of Kubernetes and are asked to update their clusters.
• End of Support: Version is not supported anymore, clusters will be automatically upgraded to the next supported minor version.

Scaleway Kubernetes products

Version information

For a complete changelog update, refer to the official Kubernetes changelog.

The following documentation only lists the main feature changes for each version and provides a link to the version release announcement on Kubernetes’ official blog.

1.31

• Official release announcement
• 45 enhancements: 11 have graduated to stable, 22 are entering beta, and 12 have graduated to alpha.

1.30

• Official release announcement
• 45 enhancements: 10 are entering alpha, 18 are have graduated to beta, and 17 graduated to stable (see announcement for full list).

1.29

• Official release announcement
• Kubernetes 1.29 includes a total of 11 enhancements promoted to stable, 19 to beta, and 19 to alpha.

1.28

• Official release announcement
• 45 enhancements: 19 are entering alpha, 14 have graduated to beta, and 12 have graduated to stable.

1.27

• Official release announcement
• This release consists of 60 enhancements. 18 of those enhancements are entering alpha, 29 are graduating to beta, and 13 are graduating to stable.

1.26

• Official release announcement
• 11 features graduated to GA, 12 features deprecated or removed.

Supported Container Network Interfaces (CNI)

Starting from Kubernetes version 1.25 launch:

• Kubernetes Kapsule only supports cilium and calico as CNI.
• Kubernetes Kosmos only supports kilo as CNI.

• Migration policy:
  • Control planes cannot be upgraded on obsolete CNIs.
  • Recommended action: Create new clusters using a supported CNI, either via API or from the Scaleway console.

Supported Container Runtime Interfaces (CRI)

Starting from the launch of Kubernetes version 1.25, containerd is the only runtime supported by Scaleway Kubernetes products.