Skip to content

Commit fb0252f

Browse files
schaffererinschaffererin
committed
resolving merge conflicts
2 parents 7d52257 + e90a573 commit fb0252f

File tree

1 file changed

+44
-33
lines changed

1 file changed

+44
-33
lines changed

‎articles/aks/supported-kubernetes-versions.md

Lines changed: 44 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Supported Kubernetes versions in Azure Kubernetes Service
3-
description: Understand the Kubernetes version support policy and lifecycle of clusters in Azure Kubernetes Service (AKS)
2+
title: Supported Kubernetes versions in Azure Kubernetes Service (AKS).
3+
description: Learn the Kubernetes version support policy and lifecycle of clusters in Azure Kubernetes Service (AKS).
44
ms.topic: article
55
ms.date: 11/21/2022
66
author: palma21
@@ -10,7 +10,7 @@ ms.custom: event-tier1-build-2022
1010

1111
# Supported Kubernetes versions in Azure Kubernetes Service (AKS)
1212

13-
The Kubernetes community releases minor versions roughly every three months. Recently, the Kubernetes community has [increased the support window for each version from nine months to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/), starting with version 1.19.
13+
The Kubernetes community releases minor versions roughly every three months. Recently, the Kubernetes community has [increased the support window for each version from nine months to 12 months](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/), starting with version *1.19*.
1414

1515
Minor version releases include new features and improvements. Patch releases are more frequent (sometimes weekly) and are intended for critical bug fixes within a minor version. Patch releases include fixes for security vulnerabilities or major bugs.
1616

@@ -57,11 +57,11 @@ For the past release history, see [Kubernetes history](https://en.wikipedia.org/
5757
> [!NOTE]
5858
> Alias minor version requires Azure CLI version 2.37 or above as well as API version 20220201 or above. Use `az upgrade` to install the latest version of the CLI.
5959
60-
With AKS, you can create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster will run the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster will run **`1.21.7`**, which is the latest GA patch version of *1.21*.
60+
AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster will run **`1.21.7`**, which is the latest GA patch version of *1.21*.
6161

62-
When you upgrade by alias minor version, only a higher minor version is supported. For example, upgrading from `1.14.x` to `1.14` won't trigger an upgrade to the latest GA `1.14` patch, but upgrading to `1.15` will trigger an upgrade to the latest GA `1.15` patch. If you wish to upgrade your patch version in the same minor version, please use [auto-upgrade](https://learn.microsoft.com/azure/aks/auto-upgrade-cluster#using-cluster-auto-upgrade).
62+
When you upgrade by alias minor version, only a higher minor version is supported. For example, upgrading from `1.14.x` to `1.14` doesn't trigger an upgrade to the latest GA `1.14` patch, but upgrading to `1.15` triggers an upgrade to the latest GA `1.15` patch.
6363

64-
To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The `currentKubernetesVersion` property shows the whole Kubernetes version.
64+
To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The property `currentKubernetesVersion` shows the whole Kubernetes version.
6565

6666
```
6767
{
@@ -86,17 +86,15 @@ AKS may also support preview versions, which are explicitly labeled and subject
8686
> [!NOTE]
8787
> AKS uses safe deployment practices which involve gradual region deployment. This means it may take up to 10 business days for a new release or a new version to be available in all regions.
8888
89-
The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest release) - 2 (minor versions)).
89+
The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest release) - 2 (minor versions)), and ".letter" is representative of patch versions.
9090

9191
For example, if AKS introduces *1.17.a* today, support is provided for the following versions:
9292

9393
New minor version | Supported Version List
9494
----------------- | ----------------------
9595
1.17.a | 1.17.a, 1.17.b, 1.16.c, 1.16.d, 1.15.e, 1.15.f
9696

97-
Where ".letter" is representative of patch versions.
98-
99-
When a new minor version is introduced, the oldest minor version and patch releases supported are deprecated and removed. For example, if the current supported version list is:
97+
When a new minor version is introduced, the oldest supported minor version and patch releases are deprecated and removed. For example, the current supported version list is:
10098

10199
```
102100
1.17.a
@@ -110,9 +108,9 @@ When a new minor version is introduced, the oldest minor version and patch relea
110108
When AKS releases 1.18.\*, all the 1.15.\* versions go out of support 30 days later.
111109

112110
> [!NOTE]
113-
> If customers are running an unsupported Kubernetes version, they'll be asked to upgrade when requesting support for the cluster. Clusters running unsupported Kubernetes releases aren't covered by the [AKS support policies](./support-policies.md).
111+
> If you're running an unsupported Kubernetes version, you'll be asked to upgrade when requesting support for the cluster. Clusters running unsupported Kubernetes releases aren't covered by the [AKS support policies](./support-policies.md).
114112
115-
In addition to the above, AKS supports a maximum of two **patch** releases of a given minor version. So given the following supported versions:
113+
AKS also supports a maximum of two **patch** releases of a given minor version. For example, given the following supported versions:
116114

117115
```
118116
Current Supported Version List
@@ -150,26 +148,39 @@ Install-AzAksKubectl -Version latest
150148

151149
---
152150

151+
## Long Term Support (LTS)
152+
153+
AKS provides a Long Term Support (LTS) version of Kubernetes for a two-year period. There's only a single minor version of Kubernetes deemed LTS at any one time.
154+
155+
| | Community Support |Long Term Support |
156+
|---|---|---|
157+
| **When to use** | When you can keep up with upstream Kubernetes releases | When you need control over when to migrate from one version to another |
158+
| **Support versions** | Three GA minor versions | One Kubernetes version (currently *1.27*) for two years |
159+
| **Pricing** | Included | Per hour cluster cost |
160+
161+
The upstream community maintains a minor release of Kubernetes for one year from release. After this period, Microsoft creates and applies security updates to the LTS version of Kubernetes to provide a total of two years of support on AKS.
162+
163+
> [!IMPORTANT]
164+
> AKS will begin its support for the LTS version of Kubernetes upon the release of Kubernetes version 1.27.
165+
153166
## Release and deprecation process
154167

155168
You can reference upcoming version releases and deprecations on the [AKS Kubernetes release calendar](#aks-kubernetes-release-calendar).
156169

157170
For new **minor** versions of Kubernetes:
158171

159-
* AKS publishes a pre-announcement with the planned date of the new version release and respective old version deprecation. This announcement is published on the [AKS release notes](https://aka.ms/aks/releasenotes) at least 30 days before removal.
160-
* AKS uses [Azure Advisor](../advisor/advisor-overview.md) to alert users if a new version will cause issues in their cluster because of deprecated APIs. Azure Advisor is also used to alert the user if they're currently out of support.
172+
* AKS publishes an announcement with the planned date of a new version release and respective old version deprecation on the [AKS Release notes](https://aka.ms/aks/releasenotes) at least 30 days prior to removal.
173+
* AKS uses [Azure Advisor](../advisor/advisor-overview.md) to alert you if a new version could cause issues in your cluster because of deprecated APIs. Azure Advisor also alerts you if you're out of support
161174
* AKS publishes a [service health notification](../service-health/service-health-overview.md) available to all users with AKS and portal access and sends an email to the subscription administrators with the planned version removal dates.
162-
163175
> [!NOTE]
164-
> Visit [manage Azure subscriptions](../cost-management-billing/manage/add-change-subscription-administrator.md#assign-a-subscription-administrator) to determine who your subscription administrators are and make any necessary changes.
165-
166-
* Users have **30 days** from version removal to upgrade to a supported minor version release to continue receiving support.
176+
> To find out who is your subscription administrators or to change it, please refer to [manage Azure subscriptions](../cost-management-billing/manage/add-change-subscription-administrator.md#assign-a-subscription-administrator).
177+
* You have **30 days** from version removal to upgrade to a supported minor version release to continue receiving support.
167178

168179
For new **patch** versions of Kubernetes:
169180

170-
* Because of the urgent nature of patch versions, they can be introduced into the service as they become available. Once available, patches will have a two month minimum lifecycle.
171-
* In general, AKS doesn't broadly communicate the release of new patch versions. However, AKS constantly monitors and validates available CVE patches to support them in AKS in a timely manner. If a critical patch is found or user action is required, AKS will notify users to upgrade to the newly available patch.
172-
* Users have **30 days** from a patch release's removal from AKS to upgrade into a supported patch and continue receiving support. However, you'll **no longer be able to create clusters or node pools once the version is deprecated/removed.**
181+
* Because of the urgent nature of patch versions, they can be introduced into the service as they become available. Once available, patches have a two month minimum lifecycle.
182+
* In general, AKS doesn't broadly communicate the release of new patch versions. However, AKS constantly monitors and validates available CVE patches to support them in AKS in a timely manner. If a critical patch is found or user action is required, AKS will notify you to upgrade to the newly available patch.
183+
* You have **30 days** from a patch release's removal from AKS to upgrade into a supported patch and continue receiving support. However, you'll **no longer be able to create clusters or node pools once the version is deprecated/removed.**
173184

174185
### Supported versions policy exceptions
175186

@@ -184,7 +195,7 @@ When you deploy an AKS cluster with Azure portal, Azure CLI, Azure PowerShell, t
184195
### [Azure CLI](#tab/azure-cli)
185196

186197
To find out what versions are currently available for your subscription and region, use the
187-
[az aks get-versions][az-aks-get-versions] command. The following example lists available Kubernetes versions for the *EastUS* region:
198+
[`az aks get-versions`][az-aks-get-versions] command. The following example lists the available Kubernetes versions for the *EastUS* region:
188199

189200
```azurecli-interactive
190201
az aks get-versions --location eastus --output table
@@ -205,13 +216,13 @@ Get-AzAksVersion -Location eastus
205216

206217
### How does Microsoft notify me of new Kubernetes versions?
207218

208-
The AKS team publishes pre-announcements with planned dates of the new Kubernetes versions in the AKS docs, our [GitHub](https://github.com/Azure/AKS/releases), and emails to subscription administrators who own clusters that are going to fall out of support. AKS also uses [Azure Advisor](../advisor/advisor-overview.md) to alert customers in the Azure portal to notify users if they're out of support. It also alerts them of deprecated APIs that will affect their application or development processes.
219+
The AKS team publishes announcements with planned dates of the new Kubernetes versions in our documentation, our [GitHub](https://github.com/Azure/AKS/releases), and in emails to subscription administrators who own clusters that are going to fall out of support. AKS also uses [Azure Advisor](../advisor/advisor-overview.md) to alert you inside the Azure portal if you're out of support and inform you of deprecated APIs that will affect your application or development process.
209220

210221
### How often should I expect to upgrade Kubernetes versions to stay in support?
211222

212-
Starting with Kubernetes 1.19, the [open source community has expanded support to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/). AKS commits to enabling patches and support matching the upstream commitments. For AKS clusters on 1.19 and greater, you'll be able to upgrade at a minimum of once a year to stay on a supported version.
223+
Starting with Kubernetes 1.19, the [open source community has expanded support to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/). AKS commits to enabling patches and support matching the upstream commitments. For AKS clusters on 1.19 and greater, you can upgrade at a minimum of once a year to stay on a supported version.
213224

214-
### What happens when a user upgrades a Kubernetes cluster with a minor version that isn't supported?
225+
**What happens when you upgrade a Kubernetes cluster with a minor version that isn't supported?**
215226

216227
If you're on the *n-3* version or older, it means you're outside of support and will be asked to upgrade. When your upgrade from version n-3 to n-2 succeeds, you're back within our support policies. For example:
217228

@@ -220,22 +231,20 @@ If you're on the *n-3* version or older, it means you're outside of support and
220231

221232
Downgrades aren't supported.
222233

223-
### What does 'Outside of Support' mean?
224-
225-
'Outside of Support' means that:
234+
**What does 'Outside of Support' mean?**
226235

227236
* The version you're running is outside of the supported versions list.
228237
* You'll be asked to upgrade the cluster to a supported version when requesting support, unless you're within the 30-day grace period after version deprecation.
229238

230239
Additionally, AKS doesn't make any runtime or other guarantees for clusters outside of the supported versions list.
231240

232-
### What happens when a user scales a Kubernetes cluster with a minor version that isn't supported?
241+
**What happens when you scale a Kubernetes cluster with a minor version that isn't supported?**
233242

234243
For minor versions not supported by AKS, scaling in or out should continue to work. Since there are no guarantees with quality of service, we recommend upgrading to bring your cluster back into support.
235244

236-
### Can a user stay on a Kubernetes version forever?
245+
**Can you stay on a Kubernetes version forever?**
237246

238-
If a cluster has been out of support for more than three (3) minor versions and has been found to carry security risks, Azure proactively contacts you to upgrade your cluster. If you don't take further action, Azure reserves the right to automatically upgrade your cluster on your behalf.
247+
If a cluster has been out of support for more than three (3) minor versions and has been found to carry security risks, Azure proactively contacts you to upgrade your cluster. If you don't take further action, Azure reserves the right to automatically upgrade your cluster on your behalf.
239248

240249
### What version does the control plane support if the node pool isn't in one of the supported AKS versions?
241250

@@ -258,11 +267,11 @@ Skipping multiple versions can only be done when upgrading from an unsupported v
258267

259268
When performing an upgrade from an _unsupported version_ that skips two or more minor versions, the upgrade is performed without any guarantee of functionality and is excluded from the service-level agreements and limited warranty. If your version is significantly out of date, it's recommended to re-create the cluster.
260269

261-
### Can I create a new 1.xx.x cluster during its 30 day support window?
270+
No. Once a version is deprecated/removed, you can't create a cluster with that version. As the change rolls out, the old version is removed from your version list. This process may take up to two weeks from announcement, progressively by region.
262271

263272
No. Once a version is deprecated/removed, you can't create a cluster with that version. As the change rolls out, you'll start to see the old version removed from your version list. This process may take up to two weeks from announcement, progressively by region.
264273

265-
### I'm on a freshly deprecated version, can I still add new node pools? Or will I have to upgrade?
274+
No, you can't add node pools of the deprecated version to your cluster. You can add node pools of a new version. However, this may require you to update the control plane first.
266275

267276
No. You won't be allowed to add node pools of the deprecated version to your cluster. You can add node pools of a new version, but this may require you to update the control plane first.
268277

@@ -280,6 +289,8 @@ For information on how to upgrade your cluster, see [Upgrade an Azure Kubernetes
280289

281290
<!-- LINKS - Internal -->
282291
[aks-upgrade]: upgrade-cluster.md
292+
[az-aks-create]: /cli/azure/aks#az_aks_create
293+
[az-aks-update]: /cli/azure/aks#az_aks_update
283294
[az-extension-add]: /cli/azure/extension#az_extension_add
284295
[az-extension-update]: /cli/azure/extension#az-extension-update
285296
[az-aks-get-versions]: /cli/azure/aks#az_aks_get_versions

0 commit comments

Comments
 (0)