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/upgrade-cluster.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -237,6 +237,7 @@ All of the following criteria must be met in order for the stop to occur:
237
237
* If performed via REST, the upgrade operation uses a preview API version of `2023-01-02-preview` or later.
238
238
* If performed via Azure CLI, the `aks-preview` CLI extension 0.5.134 or later must be installed.
239
239
* The last seen usage of deprecated APIs for the targeted version you're upgrading to must occur within 12 hours before the upgrade operation. AKS records usage hourly, so any usage of deprecated APIs within one hour isn't guaranteed to appear in the detection.
240
+
* Even API usage that is actually watching for deprecated resources is covered here. Look at the [Verb][k8s-api] for the distinction.
240
241
241
242
### Mitigating stopped upgrade operations
242
243
@@ -260,11 +261,11 @@ After receiving the error message, you have two options to mitigate the issue. Y
260
261
261
262
:::image type="content" source="./media/upgrade-cluster/applens-api-detection-inline.png" lightbox="./media/upgrade-cluster/applens-api-detection-full.png" alt-text="A screenshot of the Azure portal showing the 'Selected Kubernetes API deprecations' section.":::
262
263
263
-
3. Wait 12 hours from the time the last deprecated API usage was seen.
264
+
3. Wait 12 hours from the time the last deprecated API usage was seen. Check the verb in the deprecated api usage to know if it is a [watch][k8s-api].
264
265
265
266
4. Retry your cluster upgrade.
266
267
267
-
You can also check past API usage by enabling [Container Insights][container-insights] and exploring kube audit logs.
268
+
You can also check past API usage by enabling [Container Insights][container-insights] and exploring kube audit logs. Check the verb in the deprecated api usage to understand, if it is a [watch][k8s-api] use case.
268
269
269
270
### Bypass validation to ignore API changes
270
271
@@ -353,5 +354,6 @@ This article showed you how to upgrade an existing AKS cluster. To learn more ab
0 commit comments