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-os-image.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,31 +131,31 @@ For more information on Planned Maintenance, see [Use Planned Maintenance to sch
131
131
132
132
## Node OS auto-upgrades FAQ
133
133
134
-
* How can I check the current nodeOsUpgradeChannel value on a cluster?
134
+
### How can I check the current nodeOsUpgradeChannel value on a cluster?
135
135
136
136
Run the `az aks show` command and check the "autoUpgradeProfile" to determine what value the `nodeOsUpgradeChannel` is set to:
137
137
138
138
```azurecli-interactive
139
139
az aks show --resource-group myResourceGroup --name myAKSCluster --query "autoUpgradeProfile"
140
140
```
141
141
142
-
* How can I monitor the status of node OS auto-upgrades?
142
+
###How can I monitor the status of node OS auto-upgrades?
143
143
144
144
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].
145
145
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` ?
147
147
148
148
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`.
149
149
150
-
* Why is `SecurityPatch` recommended over `Unmanaged` channel?
150
+
###Why is `SecurityPatch` recommended over `Unmanaged` channel?
151
151
152
152
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].
153
153
154
-
* Does `SecurityPatch` always lead to a reimage of my nodes?
154
+
###Does `SecurityPatch` always lead to a reimage of my nodes?
155
155
156
156
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.
157
157
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?
0 commit comments