[zh-cn]sync endpoint-slice-v1.md

Signed-off-by: xin.li <[email protected]>

Author: my-git9

content/zh-cn/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1.md

@@ -4,13 +4,20 @@ api_metadata:
   import: "k8s.io/api/discovery/v1"
   kind: "EndpointSlice"
 content_type: "api_reference"
-description: "EndpointSlice 是实现某 Service 的端点的子集."
+description: "EndpointSlice 代表一组服务端点。"
 title: "EndpointSlice"
 weight: 3
 ---
 
 <!--
-description: "EndpointSlice represents a subset of the endpoints that implement a service."
+api_metadata:
+  apiVersion: "discovery.k8s.io/v1"
+  import: "k8s.io/api/discovery/v1"
+  kind: "EndpointSlice"
+content_type: "api_reference"
+description: "EndpointSlice represents a set of service endpoints."
+title: "EndpointSlice"
+weight: 3
 -->
 
 `apiVersion: discovery.k8s.io/v1`
@@ -20,10 +27,13 @@ description: "EndpointSlice represents a subset of the endpoints that implement
 ## EndpointSlice {#EndpointSlice}
 
 <!--
-EndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.
+EndpointSlice represents a set of service endpoints. Most EndpointSlices are created by the EndpointSlice controller to represent the Pods selected by Service objects. For a given service there may be multiple EndpointSlice objects which must be joined to produce the full set of endpoints; you can find all of the slices for a given service by listing EndpointSlices in the service's namespace whose `kubernetes.io/service-name` label contains the service's name.
 -->
-EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有多个 EndpointSlice 对象与之对应，
-必须将所有的 EndpointSlice 拼接起来才能形成一套完整的端点集合。Service 通过标签来选择 EndpointSlice。
+EndpointSlice 表示一组服务端点。大多数 EndpointSlice 由 EndpointSlice
+控制器创建，用于表示被 Service 对象选中的 Pod。对于一个给定的服务，可能存在多个
+EndpointSlice 对象，这些对象必须被组合在一起以产生完整的端点集合；
+你可以通过在服务的命名空间中列出 `kubernetes.io/service-name`
+标签包含 Service 名称的 EndpointSlices 来找到给定 Service 的所有 slices。
 
 <hr>
 
@@ -41,7 +51,7 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
 - **addressType** (string), <!--required-->必需
 
   <!--
-  addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.
+  addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name. (Deprecated) The EndpointSlice controller only generates, and kube-proxy only processes, slices of addressType "IPv4" and "IPv6". No semantics are defined for the "FQDN" type.
   -->
   addressType 指定当前 EndpointSlice 携带的地址类型。一个 EndpointSlice 只能携带同一类型的地址。
   EndpointSlice 对象创建完成后不可以再更改 addressType 字段。
@@ -50,6 +60,8 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
   * IPv4：表示 IPv4 地址。
   * IPv6：表示 IPv6 地址。
   * FQDN：表示完全限定域名。
+  * （已弃用）EndpointSlice 控制器仅生成地址类型为 "IPv4" 和 "IPv6" 的切片，
+    且 kube-proxy 也仅处理这些类型的切片。对于 "FQDN" 类型，未定义其语义。
 
 - **endpoints** ([]Endpoint), <!--required-->必需
 
@@ -79,12 +91,14 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
     **集合：不重复的值在合并期间会被保留**
 
     <!--
-    addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267
+    addresses of this endpoint. For EndpointSlices of addressType "IPv4" or "IPv6", the values are IP addresses in canonical form. The syntax and semantics of other addressType values are not defined. This must contain at least one address but no more than 100. EndpointSlices generated by the EndpointSlice controller will always have exactly 1 address. No semantics are defined for additional addresses beyond the first, and kube-proxy does not look at them.
     -->
 
-    本端点的地址。此字段的内容会根据对应的 EndpointSlice addressType 字段的值进行解释。
-    消费者必须根据自身能力处理不同类型的地址。此字段必须至少包含 1 个地址，最多不超过 100 个地址。
-    假定这些地址都是可替换的，而且客户端也可能选择只用第一个元素。参阅： https://issue.k8s.io/106267
+    本端点的地址。对于地址类型为 "IPv4" 或 "IPv6" 的 EndpointSlices，
+    值是规范形式的 IP 地址。其他地址类型值的语法和语义未定义。
+    这必须包含至少一个地址但不超过 100 个。由 EndpointSlice 控制器生成的
+    EndpointSlices 将始终只有 1 个地址。对于第一个之后的额外地址，未定义其语义，
+    并且 kube-proxy 不会查看它们。
 
   - **endpoints.conditions** (EndpointConditions)
 
@@ -105,33 +119,32 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
     - **endpoints.conditions.ready** (boolean)  
 
       <!--
-      ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be "true" for terminating endpoints, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.
+      ready indicates that this endpoint is ready to receive traffic, according to whatever system is managing the endpoint. A nil value should be interpreted as "true". In general, an endpoint should be marked ready if it is serving and not terminating, though this can be overridden in some cases, such as when the associated Service has set the publishNotReadyAddresses flag.
       -->
-      
-      ready 说明此端点已经准备好根据相关的系统映射接收流量。nil 值表示状态未知。
-      在大多数情况下，消费者应将这种未知状态视为就绪（ready）。
-      考虑到兼容性，对于正在结束状态下的端点，永远不能将 ready 设置为“true”，
-      除非正常的就绪行为被显式覆盖，例如当关联的服务设置了 publishNotReadyAddresses 标志时。
+
+      ready 说明此端点已经准备好根据相关的系统映射接收流量。nil 值应解释为 "true"。
+      通常，如果 endpoint 正在服务且未终止，则应将其标记为 ready，
+      尽管在某些情况下可以覆盖此设置，例如当关联的 Service 设置了
+      publishNotReadyAddresses 标志时。
 
     - **endpoints.conditions.serving** (boolean)
 
       <!--
-      serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition.
+      serving indicates that this endpoint is able to receive traffic, according to whatever system is managing the endpoint. For endpoints backed by pods, the EndpointSlice controller will mark the endpoint as serving if the pod's Ready condition is True. A nil value should be interpreted as "true".
       -->
       
-      serving 和 ready 非常相似。唯一的不同在于,
-      即便某端点的状态为 Terminating 也可以设置 serving。
-      对于处在终止过程中的就绪端点，此状况应被设置为 “true”。
-      如果设置为 nil，则消费者应该以 ready 值为准。
+      serving 表示此端点能够接收流量，根据管理端点的系统。对于由 Pod 支持的端点，
+      如果 Pod 的 Ready 条件为 True，EndpointSlice 控制器会将端点标记为 serving。
+      nil 值应解释为 "true"。
 
     - **endpoints.conditions.terminating** (boolean)
 
       <!--
-      terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating.
+      terminating indicates that this endpoint is terminating. A nil value should be interpreted as "false".
       -->
-      
-      terminating 说明当前端点正在终止过程中。nil 值表示状态未知。
-      消费者应将这种未知状态视为端点并不处于终止过程中。
+
+      terminating 说明当前端点正在终止过程中。
+      nil 值应解释为 "false"。
 
   - **endpoints.deprecatedTopology** (map[string]string)
 
@@ -161,6 +174,38 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
 
     **EndpointHints 提供应该如何使用某端点的提示信息。**
 
+    - **endpoints.hints.forNodes** ([]ForNode)
+
+      <!--
+      *Atomic: will be replaced during a merge*
+      -->
+      
+      **原子性：合并期间将被替换**
+
+      <!--
+      forNodes indicates the node(s) this endpoint should be consumed by when using topology aware routing. May contain a maximum of 8 entries. This is an Alpha feature and is only used when the PreferSameTrafficDistribution feature gate is enabled.
+      -->
+
+      forNodes 表示在使用拓扑感知路由时，此端点应由哪个（些）节点消费。
+      最多可能包含 8 个条目。这是一个 Alpha 级别特性，仅在启用了 PreferSameTrafficDistribution
+      特性门控时使用。
+
+      <a name="ForNode"></a>
+    
+      <!--
+      *ForNode provides information about which nodes should consume this endpoint.*
+
+      - **endpoints.hints.forNodes.name** (string), required
+
+        name represents the name of the node.
+      -->
+
+      **ForNode 提供关于哪个节点应调用此端点的信息。**
+
+      - **endpoints.hints.forNodes.name** (string)，必需
+
+        name 表示节点的名称。
+
     - **endpoints.hints.forZones** ([]ForZone)
 
       <!--
@@ -170,10 +215,11 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
       **原子性：合并期间将被替换**
 
       <!--
-      forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing.
+      forZones indicates the zone(s) this endpoint should be consumed by when using topology aware routing. May contain a maximum of 8 entries.
       -->
       
-      forZones 表示应该由哪个可用区调用此端点从才能激活拓扑感知路由。
+      forZones 表示在使用拓扑感知路由时，该端点应由哪个（些）区域消费。
+      最多可能包含 8 个条目。
 
       <a name="ForZone"></a>
 
@@ -234,12 +280,14 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
   **原子性：合并期间会被替代**
 
   <!--
-  ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates "all ports". Each slice may include a maximum of 100 ports.
+  ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. Each slice may include a maximum of 100 ports. Services always have at least 1 port, so EndpointSlices generated by the EndpointSlice controller will likewise always have at least 1 port. EndpointSlices used for other purposes may have an empty ports list.
   -->
+
 
   ports 列出了当前 EndpointSlice 中各个端点所暴露的网络端口。每个端口的名称不得重复。
-  当 ports 列表为空时，表示没有已经指定暴露哪些端口。如果端口值被定义为 nil，表示暴露“所有端口”。
-  每个 EndpointSlice 最多可以包含 100 个端口。
+  每个切片最多可能包含 100 个端口。Service 总是至少有 1 个端口，因此由 EndpointSlice
+  控制器生成的 EndpointSlices 同样总是至少有 1 个端口。用于其他目的的 EndpointSlices
+  可能有一个空的 ports 列表。
 
   <a name="EndpointPort"></a>
 
@@ -252,10 +300,11 @@ EndpointSlice 是实现某 Service 的端点的子集。一个 Service 可以有
   - **ports.port** (int32)
 
     <!--
-    port represents the port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.
+    port represents the port number of the endpoint. If the EndpointSlice is derived from a Kubernetes service, this must be set to the service's target port. EndpointSlices used for other purposes may have a nil port.
     -->
 
-    port 表示端点的端口号。如果未指定，就不限制端口，且必须根据消费者的具体环境进行解释。
+    port 表示端点的端口号。如果 EndpointSlice 是从 Kubernetes 服务派生的，
+    这必须设置为服务的目标端口。用于其他目的的 EndpointSlices 可能有一个 nil 端口。
 
   - **ports.protocol** (string)