Skip to content

Commit 7b7537e

Browse files
Apply review changes.
1 parent 752cc78 commit 7b7537e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/aks/auto-upgrade-node-image.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,14 @@ ms.date: 02/03/2023
1010

1111
# Auto-upgrade Azure Kubernetes Service cluster node OS images
1212

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.
1414

1515
## How does node OS auto-upgrade work with cluster auto-upgrade?
1616

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].
1818
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.
1919

20-
## How to auto upgrade OS images in AKS
20+
## Use node OS auto-upgrade
2121

2222
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.
2323

@@ -45,7 +45,7 @@ To set the node os auto-upgrade channel on existing cluster, update the *node-os
4545
az aks update --resource-group myResourceGroup --name myAKSCluster --node-os-upgrade-channel SecurityPatch
4646
```
4747

48-
## Update Ownership and Cadence
48+
## Update ownership and cadence
4949

5050
The default cadence means there's no planned maintenance window applied.
5151

@@ -96,7 +96,7 @@ az provider register --namespace Microsoft.ContainerService
9696

9797
## Node OS auto-upgrade with Planned Maintenance
9898

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-upgrade starts at your specified maintenance window.
100100

101101
> [!NOTE]
102102
> To ensure proper functionality, use a maintenance window of four hours or more.

0 commit comments

Comments
 (0)