Skip to content

Commit caa2605

Browse files
committed
updated to further address security patching and ICM
1 parent a9ec77e commit caa2605

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/aks/upgrade.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,16 @@ An Azure Kubernetes Service (AKS) cluster will periodically need to be updated t
1515
- *Cluster Kubernetes version*: Part of the AKS cluster lifecycle involves performing upgrades to the latest Kubernetes version. It’s important you upgrade to apply the latest security releases and to get access to the latest Kubernetes features, as well as to stay within the [AKS support window][supported-k8s-versions].
1616
- *Node image version*: AKS regularly provides new node images with the latest OS and runtime updates. It's beneficial to upgrade your nodes' images regularly to ensure support for the latest AKS features and to apply essential security patches and hot fixes.
1717

18+
For Linux nodes, node image security patches and hotfixes may be performed without your initiation as *unattended updates*. These updates are automatically applied, but AKS doesn't automatically reboot your Linux nodes to complete the update process. You're required to use a tool like [kured][node-updates-kured] or [node image upgrade][node-image-upgrade] to reboot the nodes and complete the cycle.
19+
1820
The following table summarizes the details of updating each component:
1921

2022
|Component name|Frequency of upgrade|Planned Maintenance supported|Supported operation methods|Documentation link|
2123
|--|--|--|--|--|
2224
|Cluster Kubernetes version (minor) upgrade|Roughly every three months|Yes| Automatic, Manual|[Upgrade an AKS cluster][upgrade-cluster]|
2325
|Cluster Kubernetes version upgrade to supported patch version|Approximately weekly. To determine the latest applicable version in your region, see the [AKS release tracker][release-tracker]|Yes|Automatic, Manual|[Upgrade an AKS cluster][upgrade-cluster]|
2426
|Node image version upgrade|**Linux**: weekly<br>**Windows**: monthly|Yes|Automatic, Manual|[AKS node image upgrade][node-image-upgrade]|
25-
|Security patches and hot fixes for node images|As-necessary||||
27+
|Security patches and hot fixes for node images|As-necessary|||[AKS node security patches][node-security-patches]|
2628

2729
## Automatic upgrades
2830

@@ -64,3 +66,5 @@ For more information what cluster operations may trigger specific upgrade events
6466
[ts-ip-limit]: /troubleshoot/azure/azure-kubernetes/error-code-publicipcountlimitreached
6567
[ts-quota-exceeded]: /troubleshoot/azure/azure-kubernetes/error-code-quotaexceeded
6668
[ts-subnet-full]: /troubleshoot/azure/azure-kubernetes/error-code-subnetisfull-upgrade
69+
[node-security-patches]: ./concepts-security.md#node-security-patches
70+
[node-updates-kured]: ./node-updates-kured.md

0 commit comments

Comments
 (0)