Skip to content

Commit 19e8532

Browse files
tanjunchenk8s-ci-robot
authored andcommitted
update zh-trans content/zh/docs/tasks/administer-cluster/reserve-compute-resources.md (#18448)
1 parent 8b961c4 commit 19e8532

File tree

1 file changed

+43
-0
lines changed

1 file changed

+43
-0
lines changed

content/zh/docs/tasks/administer-cluster/reserve-compute-resources.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -239,6 +239,41 @@ exist. Kubelet will fail if an invalid cgroup is specified.
239239

240240
请注意,如果 `--system-reserved-cgroup` 不存在,Kubelet **不会**创建它。如果指定了无效的 cgroup,Kubelet 将会失败。
241241

242+
<!--
243+
### Explicitly Reserved CPU List
244+
-->
245+
### 明确保留的 CPU 列表
246+
{{< feature-state for_k8s_version="v1.17" state="stable" >}}
247+
248+
- **Kubelet Flag**: `--reserved-cpus=0-3`
249+
250+
<!--
251+
`reserved-cpus` is meant to define an explicit CPU set for OS system daemons and
252+
kubernetes system daemons. This option is added in 1.17 release. `reserved-cpus`
253+
is for systems that do not intent to define separate top level cgroups for
254+
OS system daemons and kubernetes system daemons with regard to cpuset resource.
255+
If the Kubelet **does not** have `--system-reserved-cgroup` and `--kube-reserved-cgroup`,
256+
the explicit cpuset provided by `reserved-cpus` will take precedence over the CPUs
257+
defined by `--kube-reserved` and `--system-reserved` options.
258+
-->
259+
`reserved-cpus` 旨在为操作系统守护程序和 kubernetes 系统守护程序定义一个显式 cpuset。此选项在 kubernetes 1.17 版本中添加。
260+
`reserved-cpus` 适用于不打算针对 cpuset 资源为操作系统守护程序和 kubernetes 系统守护程序定义单独的顶级 cgroups 的系统。
261+
如果 Kubelet **没有** 指定参数 `--system-reserved-cgroup``--kube-reserved-cgroup`,则 `reserved-cpus` 提供的显式 cpuset 将优先于 `--kube-reserved``--system-reserved` 选项定义的 cpuset。
262+
263+
<!--
264+
This option is specifically designed for Telco/NFV use cases where uncontrolled
265+
interrupts/timers may impact the workload performance. you can use this option
266+
to define the explicit cpuset for the system/kubernetes daemons as well as the
267+
interrupts/timers, so the rest CPUs on the system can be used exclusively for
268+
workloads, with less impact from uncontrolled interrupts/timers. To move the
269+
system daemon, kubernetes daemons and interrupts/timers to the explicit cpuset
270+
defined by this option, other mechanism outside Kubernetes should be used.
271+
For example: in Centos, you can do this using the tuned toolset.
272+
-->
273+
此选项是专门为 Telco 或 NFV 用例设计的,在这些用例中不受控制的中断或计时器可能会影响其工作负载性能。
274+
可以使用此选项为系统或 kubernetes 守护程序以及中断或计时器定义显式的 cpuset,因此系统上的其余 CPU 可以专门用于工作负载,而不受不受控制的中断或计时器的影响较小。要将系统守护程序、kubernetes 守护程序和中断或计时器移动到此选项定义的显式 cpuset 上,应使用 Kubernetes 之外的其他机制。
275+
例如:在 Centos 系统中,可以使用 tuned 工具集来执行此操作。
276+
242277
<!--
243278
### Eviction Thresholds
244279
@@ -418,4 +453,12 @@ for the alpha release.
418453
截至 Kubernetes 1.7 版本,`kubelet` 支持指定 `storage``kube-reserved``system-reserved` 的资源。
419454

420455
截至 Kubernetes 1.8 版本,对于 alpha 版本,`storage` 键值名称已更改为 `ephemeral-storage`
456+
457+
<!--
458+
As of Kubernetes version 1.17, you can optionally specify
459+
explicit cpuset by `reserved-cpus` as CPUs reserved for OS system
460+
daemons/interrupts/timers and Kubernetes daemons.
461+
-->
462+
从 Kubernetes 1.17 版本开始,可以选择将 `reserved-cpus` 显式 cpuset 指定为操作系统守护程序、中断、计时器和 Kubernetes 守护程序保留的 CPU。
463+
421464
{{% /capture %}}

0 commit comments

Comments
 (0)