From 22ea7b1aeb286ef011a4813c634405a0454ad7b7 Mon Sep 17 00:00:00 2001 From: Eamon Keane Date: Tue, 9 Jan 2018 16:04:21 +0000 Subject: [PATCH] typo in `ScalingLimited` changed to just have one t --- .../run-application/horizontal-pod-autoscale-walkthrough.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index d555c8050c..05ed55219c 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -304,7 +304,7 @@ For this HorizontalPodAutoscaler, we can see several conditions in a healthy sta whether or not any backoff-related conditions would prevent scaling. The second, `ScalingActive`, indicates whether or not the HPA is enabled (i.e. the replica count of the target is not zero) and is able to calculate desired scales. When it is `False`, it generally indicates problems with -fetching metrics. Finally, the last condition, `ScalingLimitted`, indicates that the desired scale +fetching metrics. Finally, the last condition, `ScalingLimited`, indicates that the desired scale was capped by the maximum or minimum of the HorizontalPodAutoscaler. This is an indication that you may wish to raise or lower the minimum or maximum replica count constraints on your HorizontalPodAutoscaler.