Skip to content

Commit 643eda7

Browse files
authored
Update node-count-is-not-in-autoscaler-min-max-range.md
Content changes for 'Current node count isn't in the autoscaler min and max range' as part of doc refresh review on 03/25/2025 - no change
1 parent be13e6c commit 643eda7

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
@@ -1,7 +1,7 @@
11
---
22
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.
4-
ms.date: 11/14/2024
4+
ms.date: 03/25/2025
55
editor: v-jsitser
66
ms.reviewer: chiragpa, nickoman, albarqaw, v-leedennis
77
ms.service: azure-kubernetes-service

0 commit comments

Comments
 (0)