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

Merge branch 'master' into release-1.12

Browse Source
This commit is contained in:
Tim Fogarty
2018-11-01 14:10:31 -07:00
parent 9a2e390e59 a9c6b4dba0
commit f002059889
146 changed files with 4631 additions and 773 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/run-application/configure-pdb.md
+1 -1
View File
@@ -191,7 +191,7 @@ zk-pdb 2 1 7s
```
The non-zero value for `ALLOWED-DISRUPTIONS` means that the disruption controller has seen the pods,
counted the matching pods, and update the status of the PDB.
counted the matching pods, and updated the status of the PDB.
You can get more information about the status of a PDB with this command:
content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+1 -2
View File
@@ -19,7 +19,6 @@ This document walks you through an example of enabling Horizontal Pod Autoscaler
{{% /capture %}}
{{< toc >}}
{{% capture prerequisites %}}
@@ -386,7 +385,7 @@ section to your HorizontalPodAutoscaler manifest to specify that you need one wo
averageValue: 30
```
When possible, it's preferrable to use the custom metric target types instead of external metrics, since it's
When possible, it's preferable to use the custom metric target types instead of external metrics, since it's
easier for cluster administrators to secure the custom metrics API. The external metrics API potentially allows
access to any metric, so cluster administrators should take care when exposing it.
content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
+2 -3
View File
@@ -28,7 +28,6 @@ to match the observed average CPU utilization to the target specified by user.
{{% /capture %}}
{{< toc >}}
{{% capture body %}}
@@ -161,8 +160,8 @@ into a desired replica count (e.g. due to an error fetching the metrics
from the metrics APIs), scaling is skipped.
Finally, just before HPA scales the target, the scale reccomendation is recorded. The
controller considers all recommendations within a configurable window choosing the
highest recommendation from within that window. This value can be configured using the `--horizontal-pod-autoscaler-downscale-stabilization-window` flag, which defaults to 5 minutes.
controller considers all recommendations within a configurable window choosing the
highest recommendation from within that window. This value can be configured using the `--horizontal-pod-autoscaler-downscale-stabilization-window` flag, which defaults to 5 minutes.
This means that scaledowns will occur gradually, smoothing out the impact of rapidly
fluctuating metric values.
content/en/docs/tasks/run-application/rolling-update-replication-controller.md
-1
View File
@@ -42,7 +42,6 @@ Rolling updates are initiated with the `kubectl rolling-update` command:
{{% /capture %}}
{{< toc >}}
{{% capture body %}}
content/en/docs/tasks/run-application/scale-stateful-set.md
+1 -1
View File
@@ -21,7 +21,7 @@ This task shows how to scale a StatefulSet. Scaling a StatefulSet refers to incr
* StatefulSets are only available in Kubernetes version 1.5 or later.
To check your version of Kubernetes, run `kubectl version`.
* Not all stateful applications scale nicely. If you are unsure about whether to scale your StatefulSets, see [StatefulSet concepts](/docs/concepts/workloads/controllers/statefulset/) or [StatefulSet tutorial](/docs/tutorials/stateful-application/basic-stateful-set/) for futher information.
* Not all stateful applications scale nicely. If you are unsure about whether to scale your StatefulSets, see [StatefulSet concepts](/docs/concepts/workloads/controllers/statefulset/) or [StatefulSet tutorial](/docs/tutorials/stateful-application/basic-stateful-set/) for further information.
* You should perform scaling only when you are confident that your stateful application
cluster is completely healthy.