You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/auto-upgrade-node-image.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,14 +10,14 @@ ms.date: 02/03/2023
10
10
11
11
# Auto-upgrade Azure Kubernetes Service cluster node OS images
12
12
13
-
AKS now supports an exclusive channel dedicated to controlling node-level OS security updates. This channel referred to as the node OS auto-upgrade channel, can't be used for cluster-level Kubernetes version upgrades. To automatically upgrade Kubernetes versions, continue to use the cluster [auto-upgrade][Autoupgrade] channel.
13
+
AKS now supports the node OS auto-upgrade channel, an exclusive channel dedicated to controlling node-level OS security updates. This channel can't be used for cluster-level Kubernetes version upgrades.
14
14
15
15
## How does node OS auto-upgrade work with cluster auto-upgrade?
16
16
17
-
Node-level OS security updates come in at a faster cadence than the Kubernetes patch or minor version updates. So AKS introduces a separate, dedicated Node OS auto-upgrade channel. Auto-upgrades grant you flexibility and customized strategy for node-level OS security updates. You choose a separate plan for cluster-level Kubernetes version [auto-upgrades][Autoupgrade].
17
+
Node-level OS security updates are released at a faster rate than Kubernetes patch or minor version updates. The node OS auto-upgrade channel grants you flexibility and enables a customized strategy for node-level OS security updates. Then, you can choose a separate plan for cluster-level Kubernetes version [auto-upgrades][Autoupgrade].
18
18
It's highly recommended to use both cluster-level [auto-upgrades][Autoupgrade] and the node OS auto-upgrade channel together. Scheduling can be fine-tuned by applying two separate sets of [maintenance windows][planned-maintenance] - `aksManagedAutoUpgradeSchedule` for the cluster [auto-upgrade][Autoupgrade] channel and `aksManagedNodeOSUpgradeSchedule` for the node OS auto-upgrade channel.
19
19
20
-
## How to auto upgrade OS images in AKS
20
+
## Use node OS auto-upgrade
21
21
22
22
The selected channel determines the timing of upgrades. When making changes to node OS auto-upgrade channels, allow up to 24 hours for the changes to take effect.
23
23
@@ -45,7 +45,7 @@ To set the node os auto-upgrade channel on existing cluster, update the *node-os
45
45
az aks update --resource-group myResourceGroup --name myAKSCluster --node-os-upgrade-channel SecurityPatch
46
46
```
47
47
48
-
## Update Ownership and Cadence
48
+
## Update ownership and cadence
49
49
50
50
The default cadence means there's no planned maintenance window applied.
51
51
@@ -96,7 +96,7 @@ az provider register --namespace Microsoft.ContainerService
96
96
97
97
## Node OS auto-upgrade with Planned Maintenance
98
98
99
-
During Planned Maintenance for the node OS auto-upgrade, your upgrade starts during your specified maintenance window.
99
+
Planned Maintenance for the node OS auto-upgradestarts at your specified maintenance window.
100
100
101
101
> [!NOTE]
102
102
> To ensure proper functionality, use a maintenance window of four hours or more.
0 commit comments