Skip to content

Commit 50c5f7f

Browse files
authored
Merge pull request #190483 from qpetraroia/patch-8
add clarity towards patches + deprecation
2 parents 06a2f68 + 673c2b3 commit 50c5f7f

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/aks/supported-kubernetes-versions.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -156,9 +156,9 @@ For new **minor** versions of Kubernetes:
156156
* Users have **30 days** from version removal to upgrade to a supported minor version release to continue receiving support.
157157

158158
For new **patch** versions of Kubernetes:
159-
* Because of the urgent nature of patch versions, they can be introduced into the service as they become available.
159+
* 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.
160160
* In general, AKS does not 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.
161-
* Users have **30 days** from a patch release's removal from AKS to upgrade into a supported patch and continue receiving support.
161+
* Users have **30 days** from a patch release's removal from AKS to upgrade into a supported patch and continue receiving support. However, you will **no longer be able to create clusters or node pools once the version is deprecated/removed.**
162162

163163
### Supported versions policy exceptions
164164

@@ -265,6 +265,10 @@ No. Once a version is deprecated/removed, you cannot create a cluster with that
265265

266266
No. You will not be allowed to 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.
267267

268+
**How often do you update patches?**
269+
270+
Patches have a two month minimum lifecycle. To keep up to date when new patches are released, follow the [AKS Release Notes](https://github.com/Azure/AKS/releases).
271+
268272
## Next steps
269273

270274
For information on how to upgrade your cluster, see [Upgrade an Azure Kubernetes Service (AKS) cluster][aks-upgrade].

0 commit comments

Comments
 (0)