Merge pull request #38221 from my-git9/zhsync/endpoint-slices.md

[zh-cn]sync services-networking/endpoint-slices.md
This commit is contained in:
Kubernetes Prow Robot 2022-12-03 06:17:53 -08:00 committed by GitHub
commit 546607c1ea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 13 deletions

View File

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