Merge pull request #38156 from windsonsea/netplu

[zh] sync network-plugins.md

Author: k8s-ci-robot

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

@@ -4,6 +4,10 @@ content_type: concept
 weight: 10
 ---
 <!--
+reviewers:
+- dcbw
+- freehan
+- thockin
 title: Network Plugins
 content_type: concept
 weight: 10
@@ -13,14 +17,17 @@ weight: 10
 
 <!-- 
 Kubernetes {{< skew currentVersion >}} supports [Container Network Interface](http://github.com/containernetworking/cni)
-(CNI) plugins for cluster networking. You must use a CNI plugin that is compatible with your cluster and that suits your needs. Different plugins are available (both open- and closed- source) in the wider Kubernetes ecosystem. 
+(CNI) plugins for cluster networking. You must use a CNI plugin that is compatible with your
+cluster and that suits your needs. Different plugins are available (both open- and closed- source)
+in the wider Kubernetes ecosystem.
 -->
 Kubernetes {{< skew currentVersion >}} 支持用于集群联网的[容器网络接口](http://github.com/containernetworking/cni) (CNI) 插件。
 你必须使用和你的集群相兼容并且满足你的需求的 CNI 插件。
 在更广泛的 Kubernetes 生态系统中你可以使用不同的插件（开源和闭源）。
 
 <!--
-A CNI plugin is required to implement the [Kubernetes network model](/docs/concepts/services-networking/#the-kubernetes-network-model).
+A CNI plugin is required to implement the
+[Kubernetes network model](/docs/concepts/services-networking/#the-kubernetes-network-model).
 -->
 要实现 [Kubernetes 网络模型](/zh-cn/docs/concepts/services-networking/#the-kubernetes-network-model)，你需要一个 CNI 插件。
 
@@ -29,7 +36,7 @@ You must use a CNI plugin that is compatible with the
 [v0.4.0](http://github.com/containernetworking/cni/blob/spec-v0.4.0/SPEC.md) or later
 releases of the CNI specification. The Kubernetes project recommends using a plugin that is
 compatible with the [v1.0.0](http://github.com/containernetworking/cni/blob/spec-v1.0.0/SPEC.md)
-CNI specification (plugins can be compatible with multiple spec versions). 
+CNI specification (plugins can be compatible with multiple spec versions).
 -->
 你必须使用与 [v0.4.0](http://github.com/containernetworking/cni/blob/spec-v0.4.0/SPEC.md)
 或更高版本的 CNI 规范相符合的 CNI 插件。
@@ -41,7 +48,9 @@ CNI 规范的插件（插件可以兼容多个规范版本）。
 <!--
 ## Installation
 
-A Container Runtime, in the networking context, is a daemon on a node configured to provide CRI Services for kubelet. In particular, the Container Runtime must be configured to load the CNI plugins required to implement the Kubernetes network model.
+A Container Runtime, in the networking context, is a daemon on a node configured to provide CRI
+Services for kubelet. In particular, the Container Runtime must be configured to load the CNI
+plugins required to implement the Kubernetes network model.
 -->
 ## 安装   {#installation}
 
@@ -51,8 +60,10 @@ CNI 插件，从而实现 Kubernetes 网络模型。
 
 {{< note >}}
 <!--
-Prior to Kubernetes 1.24, the CNI plugins could also be managed by the kubelet using the `cni-bin-dir` and `network-plugin` command-line parameters.
-These command-line parameters were removed in Kubernetes 1.24, with management of the CNI no longer in scope for kubelet.
+Prior to Kubernetes 1.24, the CNI plugins could also be managed by the kubelet using the
+`cni-bin-dir` and `network-plugin` command-line parameters.
+These command-line parameters were removed in Kubernetes 1.24, with management of the CNI no
+longer in scope for kubelet.
 -->
 在 Kubernetes 1.24 之前，CNI 插件也可以由 kubelet 使用命令行参数 `cni-bin-dir`
 和 `network-plugin` 管理。Kubernetes 1.24 移除了这些命令行参数，
@@ -62,19 +73,22 @@ CNI 的管理不再是 kubelet 的工作。
 See [Troubleshooting CNI plugin-related errors](/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/)
 if you are facing issues following the removal of dockershim.
 -->
-如果你在移除 dockershim 之后遇到问题，请参阅[排查 CNI 插件相关的错误](/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/)。
+如果你在移除 dockershim 之后遇到问题，
+请参阅[排查 CNI 插件相关的错误](/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/)。
 {{< /note >}}
 
 <!--
-For specific information about how a Container Runtime manages the CNI plugins, see the documentation for that Container Runtime, for example:
+For specific information about how a Container Runtime manages the CNI plugins, see the
+documentation for that Container Runtime, for example:
 -->
 要了解容器运行时如何管理 CNI 插件的具体信息，可参见对应容器运行时的文档，例如：
 
 - [containerd](http://github.com/containerd/containerd/blob/main/script/setup/install-cni)
 - [CRI-O](http://github.com/cri-o/cri-o/blob/main/contrib/cni/README.md)
 
 <!--
-For specific information about how to install and manage a CNI plugin, see the documentation for that plugin or [networking provider](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model).
+For specific information about how to install and manage a CNI plugin, see the documentation for
+that plugin or [networking provider](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model).
 -->
 要了解如何安装和管理 CNI 插件的具体信息，可参阅对应的插件或
 [网络驱动（Networking Provider）](/zh-cn/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model)
@@ -83,10 +97,14 @@ For specific information about how to install and manage a CNI plugin, see the d
 <!--
 ## 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.
+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}
 
@@ -99,18 +117,24 @@ sysctl 参数设置为 `1`，以确保 iptables 代理正常工作。
 它应该确保为代理对容器通信执行正确的路由。
 
 <!--
-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.
+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 model, Kubernetes also requires the container runtimes to provide a loopback interface `lo`, which is used for each sandbox (pod sandboxes, vm sandboxes, ...).
-Implementing the loopback interface can be accomplished by re-using the [CNI loopback plugin.](http://github.com/containernetworking/plugins/blob/master/plugins/main/loopback/loopback.go) or by developing your own code to achieve this (see [this example from CRI-O](http://github.com/cri-o/ocicni/blob/release-1.24/pkg/ocicni/util_linux.go#L91)).
+In addition to the CNI plugin installed on the nodes for implementing the Kubernetes network
+model, Kubernetes also requires the container runtimes to provide a loopback interface `lo`, which
+is used for each sandbox (pod sandboxes, vm sandboxes, ...).
+Implementing the loopback interface can be accomplished by re-using the
+[CNI loopback plugin.](http://github.com/containernetworking/plugins/blob/master/plugins/main/loopback/loopback.go)
+or by developing your own code to achieve this (see
+[this example from CRI-O](http://github.com/cri-o/ocicni/blob/release-1.24/pkg/ocicni/util_linux.go#L91)).
 -->
 ### 本地回路 CNI   {#loopback-cni}
 
@@ -124,15 +148,16 @@ Implementing the loopback interface can be accomplished by re-using the [CNI loo
 <!--
 ### Support hostPort
 
-The CNI networking plugin supports `hostPort`. You can use the official [portmap](http://github.com/containernetworking/plugins/tree/master/plugins/meta/portmap)
+The CNI networking plugin supports `hostPort`. You can use the official
+[portmap](http://github.com/containernetworking/plugins/tree/master/plugins/meta/portmap)
 plugin offered by the CNI plugin team or use your own plugin with portMapping functionality.
 
-If you want to enable `hostPort` support, you must specify `portMappings capability` in your `cni-conf-dir`.
-For example:
+If you want to enable `hostPort` support, you must specify `portMappings capability` in your
+`cni-conf-dir`. For example:
 -->
 ### 支持 hostPort   {#support-hostport}
 
-CNI 网络插件支持 `hostPort`。 你可以使用官方
+CNI 网络插件支持 `hostPort`。你可以使用官方
 [portmap](http://github.com/containernetworking/plugins/tree/master/plugins/meta/portmap)
 插件，它由 CNI 插件团队提供，或者使用你自己的带有 portMapping 功能的插件。
 
@@ -173,17 +198,19 @@ CNI 网络插件支持 `hostPort`。 你可以使用官方
 
 **Experimental Feature**
 
-The CNI networking plugin also supports pod ingress and egress traffic shaping. You can use the official [bandwidth](http://github.com/containernetworking/plugins/tree/master/plugins/meta/bandwidth)
+The CNI networking plugin also supports pod ingress and egress traffic shaping. You can use the
+official [bandwidth](http://github.com/containernetworking/plugins/tree/master/plugins/meta/bandwidth)
 plugin offered by the CNI plugin team or use your own plugin with bandwidth control functionality.
 
-If you want to enable traffic shaping support, you must add the `bandwidth` plugin to your CNI configuration file
-(default `/etc/cni/net.d`) and ensure that the binary is included in your CNI bin dir (default `/opt/cni/bin`).
+If you want to enable traffic shaping support, you must add the `bandwidth` plugin to your CNI
+configuration file (default `/etc/cni/net.d`) and ensure that the binary is included in your CNI
+bin dir (default `/opt/cni/bin`).
 -->
 ### 支持流量整形   {#support-traffic-shaping}
 
 **实验功能**
 
-CNI 网络插件还支持 pod 入口和出口流量整形。
+CNI 网络插件还支持 Pod 入站和出站流量整形。
 你可以使用 CNI 插件团队提供的
 [bandwidth](http://github.com/containernetworking/plugins/tree/master/plugins/meta/bandwidth)
 插件，也可以使用你自己的具有带宽控制功能的插件。
@@ -220,12 +247,13 @@ CNI 网络插件还支持 pod 入口和出口流量整形。
   ]
 }
 ```
+
 <!--
-Now you can add the `kubernetes.io/ingress-bandwidth` and `kubernetes.io/egress-bandwidth` annotations to your pod.
-For example:
+Now you can add the `kubernetes.io/ingress-bandwidth` and `kubernetes.io/egress-bandwidth`
+annotations to your Pod. For example:
 -->
 现在，你可以将 `kubernetes.io/ingress-bandwidth` 和 `kubernetes.io/egress-bandwidth`
-注解添加到 pod 中。例如：
+注解添加到 Pod 中。例如：
 
 ```yaml
 apiVersion: v1