Skip navigation

Removing Kubernetes 1.7 and 1.8 support in AKS on 30 November 2018

Posted on 25 October 2018

On 30 November 2018, Azure Kubernetes Service (AKS) will stop supporting Kubernetes minor versions 1.7 and 1.8 (including all patch versions of both). The reduced number of minor versions supported in AKS is to simplify and remove the complexity of choosing between multiple minor Kubernetes versions. We recommend that you upgrade to one of the newer minor versions. The versions supported today include 1.7, 1.8, 1.9, 1.10 and 1.11.

Background

The Kubernetes community releases minor versions roughly every three months. These releases include new features and improvements. Patch releases are more frequent (sometimes weekly) and are only intended for critical bug fixes in a minor version. These patch releases include fixes for security vulnerabilities or major bugs that affect a large number of customers and products running in production based on Kubernetes.

A new Kubernetes minor version is made available in acs-engine on day one. The AKS Service Level Objective (SLO) targets releasing the minor version for AKS clusters within 30 days, subject to the stability of the release.

Kubernetes version support policy

AKS supports four minor versions of Kubernetes:

  • The current minor version that is released upstream (n).
  • Three previous minor versions. Each supported minor version also supports two stable patches.

For example, if AKS introduces 1.11.x today, support will also be provided for 1.10.a + 1.10.b1.9.c + 1.9d1.8.e1.8f (where the lettered patch releases are the two latest stable builds).

When a new minor version is introduced, the oldest minor version and patch releases supported will be retired. Fifteen days before the release of the new minor version and upcoming version retirement, an announcement will be made through the Azure update channels. In the previous example where 1.11.x is released, the retired versions are 1.7.g + 1.7.h.

When you deploy an AKS cluster in the portal or with the Azure CLI, the cluster is always set to the n-1 minor version and latest patch. For example, if AKS supports 1.11.x1.10.a + 1.10.b1.9.c + 1.9d1.8.e + 1.8f, the default version for new clusters is 1.10.b.

Related feedback