@@ -24,12 +24,14 @@ description: >-
24
24
{{< feature-state for_k8s_version="v1.21" state="stable" >}}
25
25
26
26
<!--
27
- _EndpointSlices_ provide a simple way to track network endpoints within a
28
- Kubernetes cluster. They offer a more scalable and extensible alternative to
29
- Endpoints.
27
+ Kubernetes' _EndpointSlices_ provide a simple way to track network endpoints
28
+ within a Kubernetes cluster. EndpointSlices offers a more scalable and extensible
29
+ alternative to Endpoints(/docs/concepts/services-networking/service/#endpoints) .
30
30
-->
31
- ** 端点切片(EndpointSlices)** 提供了一种简单的方法来跟踪 Kubernetes 集群中的网络端点(network endpoints)。
32
- 它们为 Endpoints 提供了一种可扩缩和可拓展的替代方案。
31
+ Kubernetes 的** 端点切片(EndpointSlices)** 提供了一种简单的方法来跟踪
32
+ Kubernetes 集群中的网络端点(network endpoints)。EndpointSlices 为
33
+ Endpoints(/zh-cn/docs/concepts/services-networking/service/#endpoints)
34
+ 提供了一种可扩缩和可拓展的替代方案。
33
35
34
36
<!-- body -->
35
37
@@ -429,16 +431,17 @@ at different times.
429
431
{{< note >}}
430
432
431
433
<!--
432
- Clients of the EndpointSlice API must be able to handle the situation where
433
- a particular endpoint address appears in more than one slice.
434
+ Clients of the EndpointSlice API must iterate through all the existing EndpointSlices
435
+ associated to a Service and build a complete list of unique network endpoints. It is
436
+ important to mention that endpoints may be duplicated in different EndointSlices.
434
437
435
- You can find a reference implementation for how to perform this endpoint deduplication
436
- as part of the `EndpointSliceCache` code within `kube-proxy`.
438
+ You can find a reference implementation for how to perform this endpoint aggregation
439
+ and deduplication as part of the `EndpointSliceCache` code within `kube-proxy`.
437
440
-->
438
- EndpointSlice API 的客户端必须能够处理特定端点地址出现在多个 EndpointSlice 中的情况。
439
-
440
- 你可以在 `kube-proxy` 中的 `EndpointSliceCache` 代码中找到有关如何执行这个端点去重的参考实现。
441
+ EndpointSlice API 的客户端必须遍历与 Service 关联的所有现有 EndpointSlices,
442
+ 并构建唯一网络端点的完整列表。值得一提的是端点可能在不同的 EndointSlices 中重复。
441
443
444
+ 你可以在 `kube-proxy` 中的 `EndpointSliceCache` 代码中找到有关如何执行此端点聚合和重复数据删除的参考实现。
442
445
{{< /note >}}
443
446
444
447
<!--
@@ -498,6 +501,10 @@ EndpointSlices 还支持围绕双栈网络和拓扑感知路由等新功能的
498
501
499
502
<!--
500
503
* Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
504
+ * Read the [API reference](/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/) for the EndpointSlice API
505
+ * Read the [API reference](/docs/reference/kubernetes-api/service-resources/endpoints-v1/) for the Endpoints API
501
506
-->
502
- * 阅读[使用 Service 连接到应用](/zh-cn/docs/concepts/services-networking/connect-applications-service/)
507
+ * 遵循[使用 Service 连接到应用](/zh-cn/docs/concepts/services-networking/connect-applications-service/)教程
508
+ * 阅读 EndpointSlice API 的 [API 参考](/zh-cn/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/)
509
+ * 阅读 Endpoints API 的 [API 参考](/zh-cn/docs/reference/kubernetes-api/service-resources/endpoints-v1/)
503
510
0 commit comments