Merge pull request #45437 from my-git9/autoscaling-1
[zh-cn]sync workloads/autoscaling.mdpull/45442/head
commit
140288917b
|
@ -75,7 +75,7 @@ Kubernetes 也支持工作负载的**自动扩缩**,这也是本页的重点
|
|||
<!--
|
||||
The concept of _Autoscaling_ in Kubernetes refers to the ability to automatically update an
|
||||
object that manages a set of Pods (for example a
|
||||
{{< glossary_tooltip text="Deployment" term_id="deployment" >}}.
|
||||
{{< glossary_tooltip text="Deployment" term_id="deployment" >}}).
|
||||
-->
|
||||
在 Kubernetes 中**自动扩缩**的概念是指自动更新管理一组 Pod 的能力(例如
|
||||
{{< glossary_tooltip text="Deployment" term_id="deployment" >}})。
|
||||
|
@ -113,7 +113,7 @@ There is a [walkthrough tutorial](/docs/tasks/run-application/horizontal-pod-aut
|
|||
|
||||
<!--
|
||||
You can automatically scale a workload vertically using a _VerticalPodAutoscaler_ (VPA).
|
||||
Different to the HPA, the VPA doesn't come with Kubernetes by default, but is a separate project
|
||||
Unlike the HPA, the VPA doesn't come with Kubernetes by default, but is a separate project
|
||||
that can be found [on GitHub](https://github.com/kubernetes/autoscaler/tree/9f87b78df0f1d6e142234bb32e8acbd71295585a/vertical-pod-autoscaler).
|
||||
-->
|
||||
你可以使用 VerticalPodAutoscaler (VPA) 实现工作负载的垂直扩缩。
|
||||
|
@ -144,7 +144,7 @@ At the moment, the VPA can operate in four different modes:
|
|||
{{< table caption="Different modes of the VPA" >}}
|
||||
Mode | Description
|
||||
:----|:-----------
|
||||
`Auto` | Currently `Recreate`, might change to in-place updates in the future
|
||||
`Auto` | Currently, `Recreate` might change to in-place updates in the future
|
||||
`Recreate` | The VPA assigns resource requests on pod creation as well as updates them on existing pods by evicting them when the requested resources differ significantly from the new recommendation
|
||||
`Initial` | The VPA only assigns resource requests on pod creation and never changes them later.
|
||||
`Off` | The VPA does not automatically change the resource requirements of the pods. The recommendations are calculated and can be inspected in the VPA object.
|
||||
|
@ -168,7 +168,7 @@ Mode | Description
|
|||
|
||||
<!--
|
||||
Resizing a workload in-place **without** restarting the {{< glossary_tooltip text="Pods" term_id="pod" >}}
|
||||
or its {{< glossary_tooltip text="Containers" term_id="container" >}} requires Kubernetes version 1.27 or later.<br />
|
||||
or its {{< glossary_tooltip text="Containers" term_id="container" >}} requires Kubernetes version 1.27 or later.
|
||||
Additionally, the `InPlaceVerticalScaling` feature gate needs to be enabled.
|
||||
-->
|
||||
在**不**重启 {{< glossary_tooltip text="Pod" term_id="pod" >}} 或其中{{< glossary_tooltip text="容器" term_id="container" >}}就地调整工作负载的情况下要求 Kubernetes 版本大于 1.27。
|
||||
|
@ -184,7 +184,7 @@ Additionally, the `InPlaceVerticalScaling` feature gate needs to be enabled.
|
|||
<!--
|
||||
For workloads that need to be scaled based on the size of the cluster (for example
|
||||
`cluster-dns` or other system components), you can use the
|
||||
[_Cluster Proportional Autoscaler_](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler).<br />
|
||||
[_Cluster Proportional Autoscaler_](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler).
|
||||
Just like the VPA, it is not part of the Kubernetes core, but hosted as its
|
||||
own project on GitHub.
|
||||
-->
|
||||
|
|
Loading…
Reference in New Issue