Skip to content

Commit 1032d7c

Browse files
authored
Merge pull request #123017 from PixelRobots/patch-19
Update auto-upgrade-node-os-image.md
2 parents 3d40f99 + 535dabc commit 1032d7c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -131,31 +131,31 @@ For more information on Planned Maintenance, see [Use Planned Maintenance to sch
131131
132132
## Node OS auto-upgrades FAQ
133133
134-
* How can I check the current nodeOsUpgradeChannel value on a cluster?
134+
### How can I check the current nodeOsUpgradeChannel value on a cluster?
135135
136136
Run the `az aks show` command and check the "autoUpgradeProfile" to determine what value the `nodeOsUpgradeChannel` is set to:
137137
138138
```azurecli-interactive
139139
az aks show --resource-group myResourceGroup --name myAKSCluster --query "autoUpgradeProfile"
140140
```
141141

142-
* How can I monitor the status of node OS auto-upgrades?
142+
### How can I monitor the status of node OS auto-upgrades?
143143

144144
To view the status of your node OS auto upgrades, look up [activity logs][monitor-aks] on your cluster. You can also look up specific upgrade-related events as mentioned in [Upgrade an AKS cluster][aks-upgrade]. AKS also emits upgrade-related Event Grid events. To learn more, see [AKS as an Event Grid source][aks-eventgrid].
145145

146-
* Can I change the node OS auto-upgrade channel value if my cluster auto-upgrade channel is set to `node-image` ?
146+
### Can I change the node OS auto-upgrade channel value if my cluster auto-upgrade channel is set to `node-image` ?
147147

148148
No. Currently, when you set the [cluster auto-upgrade channel][Autoupgrade] to `node-image`, it also automatically sets the node OS auto-upgrade channel to `NodeImage`. You can't change the node OS auto-upgrade channel value if your cluster auto-upgrade channel is `node-image`. In order to be able to change the node OS auto-upgrade channel values, make sure the [cluster auto-upgrade channel][Autoupgrade] isn't `node-image`.
149149

150-
* Why is `SecurityPatch` recommended over `Unmanaged` channel?
150+
### Why is `SecurityPatch` recommended over `Unmanaged` channel?
151151

152152
On the `Unmanaged` channel, AKS has no control over how and when the security updates are delivered. With `SecurityPatch`, the security updates are fully tested and follow safe deployment practices. `SecurityPatch` also honors maintenance windows. For more details, see [Increased security and resiliency of Canonical workloads on Azure][Blog].
153153

154-
* Does `SecurityPatch` always lead to a reimage of my nodes?
154+
### Does `SecurityPatch` always lead to a reimage of my nodes?
155155

156156
AKS limits reimages to only when absolutely necessary, such as certain kernel packages that may require a reimage to get fully applied. `SecurityPatch` is designed to minimize disruptions as much as possible. If AKS decides reimaging nodes isn't necessary, it will patch nodes live without draining pods and no VHD update is performed in such cases.
157157

158-
* How do I know if a `SecurityPatch` or `NodeImage` upgrade is applied on my node?
158+
### How do I know if a `SecurityPatch` or `NodeImage` upgrade is applied on my node?
159159

160160
Run the following command to obtain node labels:
161161

0 commit comments

Comments
 (0)