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 recommandation

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

Cluster auto-upgrade

The auto-upgrade functionality provided by Kubernetes Kapsule & Kubernetes Kosmos on the control plane and the managed node versions of Kubernetes can be activated using the API, CLI, or the Scaleway console. For this functionality to operate correctly, the kube-system namespace of a cluster must not be altered or have any user-induced behaviors that could interfere with the auto-upgrade functionality.

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

• Release: Version is available for 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 lists only the main feature changes for each version and provides a link to the version release announcement on Kubernetes’ official blog.

1.26

• Official release announcement Main changes:
• Eleven features graduated to GA
• Twelve features deprecated or removed

1.25

• Official release announcement Main changes:
• Thirteen enhancements graduated to GA (see announcement for full list)

1.24

• Official release announcement

1.23

• Official release announcement

Main changes:

• Deprecation of FlexVolume
• Deprecation of klog specific flags
• API/features graduation to GA (see announcement for full list)
• API/features graduation to beta (see announcement for full list)
• CSI Migration updates

1.22

• Official release announcement

Main changes:

• Removal of several deprecated beta APIs in favor of GA versions (here for more details https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/)
• Ephemeral Containers API changes and improvements

1.21

• Official release announcement

Main changes:

• PodSecurityPolicy deprecation
• TopologyKeys Deprecation

1.20

• Official release announcement

Main changes:

• Dockershim Deprecation
• Exec Probe Timeout Handling

1.19

Official release announcement

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 Kubernetes version 1.25 launch, containerd is the only runtime supported by Scaleway Kubernetes products.

• Migration policies:
  • Pools using deprecated CRIs cannot scale up.
  • Control Planes cannot be upgraded if CRI used by any pool is obsolete.
  • Recommended action: Delete your old pools and create new ones with containerd as default, either via API or from the Scaleway console.