sync endpoint-slice pod-lifecycle extend-service-ip-ranges

Author: asa3311

content/zh-cn/docs/concepts/services-networking/endpoint-slices.md

@@ -28,12 +28,7 @@ description: >-
 
 {{< feature-state for_k8s_version="v1.21" state="stable" >}}
 
-<!--
-Kubernetes' _EndpointSlice_ API provides a way to track network endpoints
-within a Kubernetes cluster.
--->
-Kubernetes 的 _EndpointSlice_ API 提供了一种简单的方法来跟踪
-Kubernetes 集群中的网络端点（network endpoints）。
+{{< glossary_definition term_id="endpoint-slice" length="short" >}}
 
 <!-- body -->
 

content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -1163,9 +1163,9 @@ containers:
 
 `readinessProbe`
 : Indicates whether the container is ready to respond to requests.
-  If the readiness probe fails, the EndpointSlice controller removes the Pod's IP
-  address from the EndpointSlices of all Services that match the Pod. The default
-  state of readiness before the initial delay is `Failure`. If a container does
+  If the readiness probe fails, the {{< glossary_tooltip term_id="endpoint-slice" text="EndpointSlice" >}}
+  controller removes the Pod's IP address from the EndpointSlices of all Services that match the Pod.
+  The default state of readiness before the initial delay is `Failure`. If a container does
   not provide a readiness probe, the default state is `Success`.
 
 `startupProbe`
@@ -1183,7 +1183,8 @@ containers:
 
 `readinessProbe`
 : 指示容器是否准备好为请求提供服务。如果就绪态探测失败，
-  EndpointSlice 控制器将从与该 Pod 匹配的所有 Service 的 EndpointSlice 中删除该 Pod 的 IP 地址。
+  {{< glossary_tooltip term_id="endpoint-slice" text="EndpointSlice" >}} 
+  控制器将从与该 Pod 匹配的所有 Service 的 EndpointSlice 中删除该 Pod 的 IP 地址。
   初始延迟之前的就绪态的状态值默认为 `Failure`。
   如果容器不提供就绪态探针，则默认状态为 `Success`。
 

content/zh-cn/docs/tasks/network/extend-service-ip-ranges.md

@@ -47,13 +47,13 @@ While you can use this feature with an earlier version, the feature is only GA a
 <!--
 Kubernetes clusters with kube-apiservers that have enabled the `MultiCIDRServiceAllocator`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and have the
-`networking.k8s.io/v1beta1` API group active, will create a ServiceCIDR object that takes
+`networking.k8s.io/v1` API group active, will create a ServiceCIDR object that takes
 the well-known name `kubernetes`, and that specifies an IP address range
 based on the value of the `--service-cluster-ip-range` command line argument to kube-apiserver.
 -->
 如果 Kubernetes 集群的 kube-apiserver 启用了 `MultiCIDRServiceAllocator`
 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)且激活了
-`networking.k8s.io/v1beta1` API 组，集群将创建一个新的 ServiceCIDR 对象，
+`networking.k8s.io/v1` API 组，集群将创建一个新的 ServiceCIDR 对象，
 该对象采用 `kubernetes` 这个众所周知的名称并基于 kube-apiserver 的 `--service-cluster-ip-range`
 命令行参数的值来使用 IP 地址范围。
 
@@ -159,7 +159,7 @@ that extends or adds new IP address ranges.
 
 ```sh
 cat <EOF | kubectl apply -f -
-apiVersion: networking.k8s.io/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: ServiceCIDR
 metadata:
   name: newcidr1
@@ -216,7 +216,7 @@ kubectl get servicecidr newcidr1 -o yaml
 ```
 
 ```yaml
-apiVersion: networking.k8s.io/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: ServiceCIDR
 metadata:
   creationTimestamp: "2023-10-12T15:11:07Z"
@@ -353,7 +353,7 @@ spec:
   matchConstraints:
     resourceRules:
     - apiGroups:   ["networking.k8s.io"]
-      apiVersions: ["v1","v1beta1"]
+      apiVersions: ["v1"]
       operations:  ["CREATE", "UPDATE"]
       resources:   ["servicecidrs"]
   matchConditions:
@@ -403,7 +403,7 @@ spec:
   matchConstraints:
     resourceRules:
     - apiGroups:   ["networking.k8s.io"]
-      apiVersions: ["v1","v1beta1"]
+      apiVersions: ["v1"]
       operations:  ["CREATE", "UPDATE"]
       resources:   ["servicecidrs"]
   validations: