Merge pull request #38565 from windsonsea/topman

[zh] sync topology-manager.md

Author: k8s-ci-robot

content/zh-cn/docs/tasks/administer-cluster/topology-manager.md

@@ -428,6 +428,54 @@ that have the `Topology Affinity` error.
 建议使用多副本的 Deployment 来触发重新部署 Pod。
 还可以通过实现外部控制环，以触发重新部署具有 `Topology Affinity` 错误的 Pod。
 
+<!--
+### Topology manager policy options
+
+Support for the Topology Manager policy options requires `TopologyManagerPolicyOptions`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled.
+-->
+### 拓扑管理器策略选项  {#topology-manager-policy-options}
+
+对拓扑管理器策略选项的支持需要启用 `TopologyManagerPolicyOptions`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
+
+<!--
+You can toggle groups of options on and off based upon their maturity level using the following feature gates:
+* `TopologyManagerPolicyBetaOptions` default disabled. Enable to show beta-level options. Currently there are no beta-level options.
+* `TopologyManagerPolicyAlphaOptions` default disabled. Enable to show alpha-level options. You will still have to enable each option using the `TopologyManagerPolicyOptions` kubelet option.
+-->
+你可以使用以下特性门控根据成熟度级别打开和关闭这些选项组：
+* `TopologyManagerPolicyBetaOptions` 默认禁用。启用以显示 Beta 级别选项。目前没有 Beta 级别选项。
+* `TopologyManagerPolicyAlphaOptions` 默认禁用。启用以显示 Alpha 级别选项。你仍然需要使用
+  `TopologyManagerPolicyOptions` kubelet 选项来启用每个选项。
+
+<!--
+The following policy options exists:
+* `prefer-closest-numa-nodes` (alpha, invisible by default, `TopologyManagerPolicyOptions` and `TopologyManagerPolicyAlphaOptions` feature gates have to be enabled)(1.26 or higher)
+-->
+存在以下策略选项：
+* `prefer-closest-numa-nodes`（Alpha，默认不可见，`TopologyManagerPolicyOptions` 和
+  `TopologyManagerPolicyAlphaOptions` 特性门控必须被启用）（1.26 或更高版本）
+
+<!--
+If the `prefer-closest-numa-nodes` policy option is specified, the `best-effort` and `restricted`
+policies will favor sets of NUMA nodes with shorter distance between them when making admission decisions.
+You can enable this option by adding `prefer-closest-numa-nodes=true` to the Topology Manager policy options.
+By default, without this option, Topology Manager aligns resources on either a single NUMA node or
+the minimum number of NUMA nodes (in cases where more than one NUMA node is required). However,
+the `TopologyManager` is not aware of NUMA distances and does not take them into account when making admission decisions.
+This limitation surfaces in multi-socket, as well as single-socket multi NUMA systems,
+and can cause significant performance degradation in latency-critical execution and high-throughput applications if the
+Topology Manager decides to align resources on non-adjacent NUMA nodes.
+-->
+如果 `prefer-closest-numa-nodes` 策略选项被指定，则在做出准入决策时 `best-effort` 和 `restricted`
+策略将偏向于彼此之间距离较短的一组 NUMA 节点。
+你可以通过将 `prefer-closest-numa-nodes=true` 添加到拓扑管理器策略选项来启用此选项。
+默认情况下，如果没有此选项，拓扑管理器会在单个 NUMA 节点或（在需要多个 NUMA 节点时）最小数量的 NUMA 节点上对齐资源。
+然而，`TopologyManager` 无法感知到 NUMA 距离且在做出准入决策时也没有考虑这些距离。
+这种限制出现在多插槽以及单插槽多 NUMA 系统中，如果拓扑管理器决定在非相邻 NUMA 节点上对齐资源，
+可能导致对执行延迟敏感和高吞吐的应用程序出现明显的性能下降。
+
 <!--
 ### Pod Interactions with Topology Manager Policies