You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh-cn/docs/setup/best-practices/cluster-large.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,7 +196,7 @@ many nodes, consider the following:
196
196
as you scale out your cluster.
197
197
* Many addons scale horizontally - you add capacity by running more pods - but with
198
198
a very large cluster you may also need to raise CPU or memory limits slightly.
199
-
The VerticalPodAutoscaler can run in _recommender_ mode to provide suggested
199
+
The [Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) can run in _recommender_ mode to provide suggested
200
200
figures for requests and limits.
201
201
* Some addons run as one copy per node, controlled by a {{< glossary_tooltip text="DaemonSet"
202
202
term_id="daemonset" >}}: for example, a node-level log aggregator. Similar to
@@ -209,8 +209,8 @@ many nodes, consider the following:
209
209
对于这些附加组件,请在扩大集群时加大资源请求和资源限制。
210
210
* 许多水平扩展插件 —— 你可以通过运行更多的 Pod 来增加容量——但是在大规模集群下,
211
211
可能还需要稍微提高 CPU 或内存限制。
212
-
VerticalPodAutoscaler 可以在 **recommender** 模式下运行,
213
-
以提供有关请求和限制的建议数字。
212
+
[Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme)
0 commit comments