whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Patch #4118 for typos

Browse Source
This commit is contained in:
Andrew Chen
2017-06-21 14:50:54 -07:00
parent 0ac6a9546a
commit 692d9a42b4
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+4 -4
View File
@@ -180,7 +180,7 @@ the only other supported resource metric is memory. These resources do not chan
to cluster, and should always be available, as long as Heapster is deployed.
You can also specify resource metrics in terms of direct values, instead of as percentages of the
requested value. To do so, use the `targetAverageValue` field insted of the `targetAverageUtilization`
requested value. To do so, use the `targetAverageValue` field instead of the `targetAverageUtilization`
field.
There are two other types of metrics, both of which are considered *custom metrics*: pod metrics and
@@ -296,7 +296,7 @@ Conditions:
Type Status Reason Message
---- ------ ------ -------
AbleToScale True ReadyForNewScale the last scale time was sufficiently old as to warrant a new scale
ScalingActive True ValidMetricFound the HPA was able to succesfully calculate a replica count from pods metric http_requests
ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from pods metric http_requests
ScalingLimited False DesiredWithinRange the desired replica count is within the acceptible range
Events:
```
@@ -307,8 +307,8 @@ whether or not any backoff-related conditions would prevent scaling. The second
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
was capped by the maximum or minimum of the HorizontalPodAutoscaler. This is an indicatation that
you may wish to raise or lower the mimimum or maximum replica count constrains on your
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.
## Appendix: Other possible scenarios