[zh-cn]sync network-plugins field-selectors replicaset statefulset

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

Author: my-git9

content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md

@@ -21,7 +21,7 @@ Kubernetes {{< skew currentVersion >}} supports [Container Network Interface](ht
 cluster and that suits your needs. Different plugins are available (both open- and closed- source)
 in the wider Kubernetes ecosystem.
 -->
-Kubernetes {{< skew currentVersion >}} 支持用于集群联网的[容器网络接口](https://github.com/containernetworking/cni) (CNI) 插件。
+Kubernetes {{< skew currentVersion >}} 支持用于集群联网的[容器网络接口](https://github.com/containernetworking/cni)（CNI）插件。
 你必须使用和你的集群相兼容并且满足你的需求的 CNI 插件。
 在更广泛的 Kubernetes 生态系统中你可以使用不同的插件（开源和闭源）。
 
@@ -97,35 +97,6 @@ that plugin or [networking provider](/docs/concepts/cluster-administration/netwo
 <!--
 ## Network Plugin Requirements
 
-For plugin developers and users who regularly build or deploy Kubernetes, the plugin may also need
-specific configuration to support kube-proxy. The iptables proxy depends on iptables, and the
-plugin may need to ensure that container traffic is made available to iptables. For example, if
-the plugin connects containers to a Linux bridge, the plugin must set the
-`net/bridge/bridge-nf-call-iptables` sysctl to `1` to ensure that the iptables proxy functions
-correctly. If the plugin does not use a Linux bridge, but uses something like Open vSwitch or
-some other mechanism instead, it should ensure container traffic is appropriately routed for the
-proxy.
--->
-## 网络插件要求   {#network-plugin-requirements}
-
-对于插件开发人员以及时常会构建并部署 Kubernetes 的用户而言，
-插件可能也需要特定的配置来支持 kube-proxy。
-iptables 代理依赖于 iptables，插件可能需要确保 iptables 能够监控容器的网络通信。
-例如，如果插件将容器连接到 Linux 网桥，插件必须将 `net/bridge/bridge-nf-call-iptables`
-sysctl 参数设置为 `1`，以确保 iptables 代理正常工作。
-如果插件不使用 Linux 网桥，而是使用类似于 Open vSwitch 或者其它一些机制，
-它应该确保为代理对容器通信执行正确的路由。
-
-<!--
-By default, if no kubelet network plugin is specified, the `noop` plugin is used, which sets
-`net/bridge/bridge-nf-call-iptables=1` to ensure simple configurations (like Docker with a bridge)
-work correctly with the iptables proxy.
--->
-默认情况下，如果未指定 kubelet 网络插件，则使用 `noop` 插件，
-该插件设置 `net/bridge/bridge-nf-call-iptables=1`，以确保简单的配置
-（如带网桥的 Docker）与 iptables 代理正常工作。
-
-<!--
 ### Loopback CNI
 
 In addition to the CNI plugin installed on the nodes for implementing the Kubernetes network
@@ -136,6 +107,8 @@ Implementing the loopback interface can be accomplished by re-using the
 or by developing your own code to achieve this (see
 [this example from CRI-O](https://github.com/cri-o/ocicni/blob/release-1.24/pkg/ocicni/util_linux.go#L91)).
 -->
+## 网络插件要求   {#network-plugin-requirements}
+
 ### 本地回路 CNI   {#loopback-cni}
 
 除了安装到节点上用于实现 Kubernetes 网络模型的 CNI 插件外，Kubernetes
@@ -218,7 +191,7 @@ CNI 网络插件还支持 Pod 入站和出站流量整形。
 
 如果你想要启用流量整形支持，你必须将 `bandwidth` 插件添加到 CNI 配置文件
 （默认是 `/etc/cni/net.d`）并保证该可执行文件包含在你的 CNI 的 bin
-文件夹内 (默认为 `/opt/cni/bin`)。
+文件夹内（默认为 `/opt/cni/bin`）。
 
 ```json
 {

content/zh-cn/docs/concepts/overview/working-with-objects/field-selectors.md

@@ -64,14 +64,33 @@ kubectl get ingress --field-selector foo.bar=baz
 Error from server (BadRequest): Unable to find "ingresses" that match label selector "", field selector "foo.bar=baz": "foo.bar" is not a known field selector: only "metadata.name", "metadata.namespace"
 ```
 
+<!--
+### List of supported fields
+
+| Kind                      | Fields                                                                                                                                                                                                                                                          |
+-->
+### 支持字段列表
+
+| 类别                       | 字段                                                                                                                                                                                                                                                            |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pod                       | `spec.nodeName`<br>`spec.restartPolicy`<br>`spec.schedulerName`<br>`spec.serviceAccountName`<br>`spec.hostNetwork`<br>`status.phase`<br>`status.podIP`<br>`status.nominatedNodeName`                                                                            |
+| Event                     | `involvedObject.kind`<br>`involvedObject.namespace`<br>`involvedObject.name`<br>`involvedObject.uid`<br>`involvedObject.apiVersion`<br>`involvedObject.resourceVersion`<br>`involvedObject.fieldPath`<br>`reason`<br>`reportingComponent`<br>`source`<br>`type` |
+| Secret                    | `type`                                                                                                                                                                                                                                                          |
+| Namespace                 | `status.phase`                                                                                                                                                                                                                                                  |
+| ReplicaSet                | `status.replicas`                                                                                                                                                                                                                                               |
+| ReplicationController     | `status.replicas`                                                                                                                                                                                                                                               |
+| Job                       | `status.successful`                                                                                                                                                                                                                                             |
+| Node                      | `spec.unschedulable`                                                                                                                                                                                                                                            |
+| CertificateSigningRequest | `spec.signerName`                                                                                                                                                                                                                                               |
+
 <!--
 ## Supported operators
 
 You can use the `=`, `==`, and `!=` operators with field selectors (`=` and `==` mean the same thing). This `kubectl` command, for example, selects all Kubernetes Services that aren't in the `default` namespace:
 -->
 ## 支持的操作符   {#supported-operators}
 
-你可在字段选择器中使用 `=`、`==` 和 `!=` （`=` 和 `==` 的意义是相同的）操作符。
+你可在字段选择器中使用 `=`、`==` 和 `!=`（`=` 和 `==` 的意义是相同的）操作符。
 例如，下面这个 `kubectl` 命令将筛选所有不属于 `default` 命名空间的 Kubernetes 服务：
 
 ```shell

content/zh-cn/docs/concepts/workloads/controllers/replicaset.md

@@ -1,5 +1,8 @@
 ---
 title: ReplicaSet
+api_metadata:
+- apiVersion: "apps/v1"
+  kind: "ReplicaSet"
 feature:
   title: 自我修复
   anchor: ReplicationController 如何工作
@@ -20,6 +23,9 @@ reviewers:
 - bprashanth
 - madhusudancs
 title: ReplicaSet
+api_metadata:
+- apiVersion: "apps/v1"
+  kind: "ReplicaSet"
 feature:
   title: Self-healing
   anchor: How a ReplicaSet works
@@ -165,15 +171,14 @@ Namespace:    default
 Selector:     tier=frontend
 Labels:       app=guestbook
               tier=frontend
-Annotations:  kubectl.kubernetes.io/last-applied-configuration:
-                {"apiVersion":"apps/v1","kind":"ReplicaSet","metadata":{"annotations":{},"labels":{"app":"guestbook","tier":"frontend"},"name":"frontend",...
+Annotations:  <none>
 Replicas:     3 current / 3 desired
 Pods Status:  3 Running / 0 Waiting / 0 Succeeded / 0 Failed
 Pod Template:
   Labels:  tier=frontend
   Containers:
    php-redis:
-    Image:        gcr.io/google_samples/gb-frontend:v3
+    Image:        us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5
     Port:         <none>
     Host Port:    <none>
     Environment:  <none>
@@ -182,9 +187,9 @@ Pod Template:
 Events:
   Type    Reason            Age   From                   Message
   ----    ------            ----  ----                   -------
-  Normal  SuccessfulCreate  117s  replicaset-controller  Created pod: frontend-wtsmm
-  Normal  SuccessfulCreate  116s  replicaset-controller  Created pod: frontend-b2zdv
-  Normal  SuccessfulCreate  116s  replicaset-controller  Created pod: frontend-vcmts
+  Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-gbgfx
+  Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-rwz57
+  Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-wkl7w
 ```
 
 <!--
@@ -203,9 +208,9 @@ You should see Pod information similar to:
 
 ```
 NAME             READY   STATUS    RESTARTS   AGE
-frontend-b2zdv   1/1     Running   0          6m36s
-frontend-vcmts   1/1     Running   0          6m36s
-frontend-wtsmm   1/1     Running   0          6m36s
+frontend-gbgfx   1/1     Running   0          10m
+frontend-rwz57   1/1     Running   0          10m
+frontend-wkl7w   1/1     Running   0          10m
 ```
 
 <!--
@@ -216,7 +221,7 @@ To do this, get the yaml of one of the Pods running:
 要实现这点，可取回运行中的某个 Pod 的 YAML：
 
 ```shell
-kubectl get pods frontend-b2zdv -o yaml
+kubectl get pods frontend-gbgfx -o yaml
 ```
 
 <!--
@@ -229,19 +234,19 @@ The output will look similar to this, with the frontend ReplicaSet's info set in
 apiVersion: v1
 kind: Pod
 metadata:
-  creationTimestamp: "2020-02-12T07:06:16Z"
+  creationTimestamp: "2024-02-28T22:30:44Z"
   generateName: frontend-
   labels:
     tier: frontend
-  name: frontend-b2zdv
+  name: frontend-gbgfx
   namespace: default
   ownerReferences:
   - apiVersion: apps/v1
     blockOwnerDeletion: true
     controller: true
     kind: ReplicaSet
     name: frontend
-    uid: f391f6db-bb9b-4c09-ae74-6a1f77f3d5cf
+    uid: e129deca-f864-481b-bb16-b27abfd92292
 ...
 ```
 

content/zh-cn/docs/concepts/workloads/controllers/statefulset.md

@@ -84,8 +84,8 @@ that provides a set of stateless replicas.
 
 <!--
 * The storage for a given Pod must either be provisioned by a
-  [PersistentVolume Provisioner](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/README.md)
-  based on the requested `storage class`, or pre-provisioned by an admin.
+  [PersistentVolume Provisioner](/docs/concepts/storage/dynamic-provisioning/) ([examples here](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/README.md))
+  based on the requested _storage class_, or pre-provisioned by an admin.
 * Deleting and/or scaling a StatefulSet down will *not* delete the volumes associated with the
   StatefulSet. This is done to ensure data safety, which is generally more valuable than an
   automatic purge of all related StatefulSet resources.
@@ -101,8 +101,9 @@ that provides a set of stateless replicas.
   [manual intervention to repair](#forced-rollback).
 -->
 * 给定 Pod 的存储必须由
-  [PersistentVolume Provisioner](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/README.md)
-  基于所请求的 `storage class` 来制备，或者由管理员预先制备。
+  [PersistentVolume Provisioner](/zh-cn/docs/concepts/storage/dynamic-provisioning/)
+  （[例子在这里](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/README.md)）
+  基于所请求的 **storage class** 来制备，或者由管理员预先制备。
 * 删除或者扩缩 StatefulSet 并**不会**删除它关联的存储卷。
   这样做是为了保证数据安全，它通常比自动清除 StatefulSet 所有相关的资源更有价值。
 * StatefulSet 当前需要[无头服务](/zh-cn/docs/concepts/services-networking/service/#headless-services)来负责 Pod
@@ -222,15 +223,24 @@ validation error during StatefulSet creation.
 <!--
 ### Volume Claim Templates
 
-You can set the `.spec.volumeClaimTemplates` which can provide stable storage using
-[PersistentVolumes](/docs/concepts/storage/persistent-volumes/) provisioned by a PersistentVolume
-Provisioner.
+You can set the `.spec.volumeClaimTemplates` field to create a
+[PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/).
+This will provide stable storage to the StatefulSet if either
 -->
 ### 卷申领模板  {#volume-claim-templates}
 
-你可以设置 `.spec.volumeClaimTemplates`，
-它可以使用 PersistentVolume 制备程序所准备的
-[PersistentVolumes](/zh-cn/docs/concepts/storage/persistent-volumes/) 来提供稳定的存储。
+你可以设置 `.spec.volumeClaimTemplates` 字段来创建
+[PersistentVolumeClaim](/zh-cn/docs/concepts/storage/persistent-volumes/)。
+这将为 StatefulSet 提供稳定的存储，如果：
+
+<!--
+* The StorageClass specified for the volume claim is set up to use [dynamic
+  provisioning](/docs/concepts/storage/dynamic-provisioning/), or
+* The cluster already contains a PersistentVolume with the correct StorageClass
+  and sufficient available storage space.
+-->
+* 为卷申领指定的 StorageClass 配置使用[动态制备](/zh-cn/docs/concepts/storage/dynamic-provisioning/)，或
+* 集群已包含具有正确 StorageClass 和足够可用存储空间的 PersistentVolume。
 
 <!--
 ### Minimum ready seconds