Skip to content

Commit d14dd58

Browse files
author
Simonx Xu
authored
Add reviewer to documentation file
1 parent 643eda7 commit d14dd58

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

support/azure/azure-kubernetes/create-upgrade-delete/node-count-is-not-in-autoscaler-min-max-range.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Current node count isn't in the autoscaler min and max range
33
description: Troubleshoot why the current node count isn't in the autoscaler minimum and maximum range when you resume an Azure Kubernetes Service cluster after a stop operation.
44
ms.date: 03/25/2025
55
editor: v-jsitser
6-
ms.reviewer: chiragpa, nickoman, albarqaw, v-leedennis
6+
ms.reviewer: chiragpa, nickoman, albarqaw, v-leedennis, wonkilee
77
ms.service: azure-kubernetes-service
88
keywords:
99
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot why the current node count isn't in the autoscaler "min" and "max" range so that I can successfully resume my Azure Kubernetes Service (AKS) cluster after a stop operation.

0 commit comments

Comments
 (0)