diff --git a/content/zh-cn/docs/concepts/cluster-administration/addons.md b/content/zh-cn/docs/concepts/cluster-administration/addons.md
index 88514c9729..93d3df1374 100644
--- a/content/zh-cn/docs/concepts/cluster-administration/addons.md
+++ b/content/zh-cn/docs/concepts/cluster-administration/addons.md
@@ -10,11 +10,11 @@ content_type: concept
 <!--
 Add-ons extend the functionality of Kubernetes.
 
-This page lists some of the available add-ons and links to their respective installation instructions.
+This page lists some of the available add-ons and links to their respective installation instructions. The list does not try to be exhaustive.
 -->
 Add-ons 扩展了 Kubernetes 的功能。
 
-本文列举了一些可用的 add-ons 以及到它们各自安装说明的链接。
+本文列举了一些可用的 add-ons 以及到它们各自安装说明的链接。该列表并不试图详尽无遗。
 
 <!-- body -->
 
@@ -66,16 +66,14 @@ Add-ons 扩展了 Kubernetes 的功能。
   而且包含了在 Kubernetes 中基于 SRIOV、DPDK、OVS-DPDK 和 VPP 的工作负载。
 <!--
 * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/) is a networking provider for Kubernetes based on [OVN (Open Virtual Network)](https://github.com/ovn-org/ovn/), a virtual networking implementation that came out of the Open vSwitch (OVS) project. OVN-Kubernetes provides an overlay based networking implementation for Kubernetes, including an OVS based implementation of load balancing and network policy.
-* [OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin) is OVN based CNI controller plugin to provide cloud native based Service function chaining(SFC), Multiple OVN overlay networking, dynamic subnet creation, dynamic creation of virtual networks, VLAN Provider network, Direct provider network and pluggable with other Multi-network plugins, ideal for edge based cloud native workloads in Multi-cluster networking.
+* [Nodus](https://github.com/akraino-edge-stack/icn-nodus) is an OVN based CNI controller plugin to provide cloud native based Service function chaining(SFC).
 -->
 * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/) 是一个 Kubernetes 网络驱动，
   基于 [OVN（Open Virtual Network）](https://github.com/ovn-org/ovn/)实现，是从 Open vSwitch (OVS)
   项目衍生出来的虚拟网络实现。OVN-Kubernetes 为 Kubernetes 提供基于覆盖网络的网络实现，
   包括一个基于 OVS 实现的负载均衡器和网络策略。
-* [OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin) 是一个基于 OVN 的 CNI 控制器插件，
-  提供基于云原生的服务功能链条（Service Function Chaining，SFC）、多种 OVN 覆盖网络、动态子网创建、
-  动态虚拟网络创建、VLAN 驱动网络、直接驱动网络，并且可以驳接其他的多网络插件，
-  适用于基于边缘的、多集群联网的云原生工作负载。
+* [Nodus](https://github.com/akraino-edge-stack/icn-nodus) 是一个基于 OVN 的 CNI 控制器插件，
+  提供基于云原生的服务功能链 (SFC)。
 <!--
 * [NSX-T](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/index.html) Container Plug-in (NCP) provides integration between VMware NSX-T and container orchestrators such as Kubernetes, as well as integration between NSX-T and container-based CaaS/PaaS platforms such as Pivotal Container Service (PKS) and OpenShift.
 * [Nuage](https://github.com/nuagenetworks/nuage-kubernetes/blob/v5.1.1-1/docs/kubernetes-1-installation.rst) is an SDN platform that provides policy-based networking between Kubernetes Pods and non-Kubernetes environments with visibility and security monitoring.
diff --git a/content/zh-cn/docs/concepts/cluster-administration/networking.md b/content/zh-cn/docs/concepts/cluster-administration/networking.md
index 9c8fcae681..f68a9d4f15 100644
--- a/content/zh-cn/docs/concepts/cluster-administration/networking.md
+++ b/content/zh-cn/docs/concepts/cluster-administration/networking.md
@@ -58,416 +58,21 @@ Kubernetes 的宗旨就是在应用之间共享机器。
 
 要了解 Kubernetes 网络模型，请参阅[此处](/zh-cn/docs/concepts/services-networking/)。
 <!--
-## How to implement the Kubernetes networking model
+## How to implement the Kubernetes network model
 
-There are a number of ways that this network model can be implemented.  This
-document is not an exhaustive study of the various methods, but hopefully serves
-as an introduction to various technologies and serves as a jumping-off point.
+The network model is implemented by the container runtime on each node. The most common container runtimes use [Container Network Interface](https://github.com/containernetworking/cni) (CNI) plugins to manage their network and security capabilities. Many different CNI plugins exist from many different vendors. Some of these provide only basic features of adding and removing network interfaces, while others provide more sophisticated solutions, such as integration with other container orchestration systems, running multiple CNI plugins, advanced IPAM features etc.
 
-The following networking options are sorted alphabetically - the order does not
-imply any preferential status.
+See [this page](/docs/concepts/cluster-administration/addons/#networking-and-network-policy) for a non-exhaustive list of networking addons supported by Kubernetes.
 -->
-## 如何实现 Kubernetes 的网络模型    {#how-to-implement-the-kubernetes-networking-model}
+## 如何实现 Kubernetes 的网络模型    {#how-to-implement-the-kubernetes-network-model}
 
-有很多种方式可以实现这种网络模型，本文档并不是对各种实现技术的详细研究，
-但是希望可以作为对各种技术的详细介绍，并且成为你研究的起点。
+网络模型由每个节点上的容器运行时实现。最常见的容器运行时使用
+[Container Network Interface](https://github.com/containernetworking/cni) (CNI) 插件来管理其网络和安全功能。
+许多不同的 CNI 插件来自于许多不同的供应商。其中一些仅提供添加和删除网络接口的基本功能，
+而另一些则提供更复杂的解决方案，例如与其他容器编排系统集成、运行多个 CNI 插件、高级 IPAM 功能等。
 
-接下来的网络技术是按照首字母排序，顺序本身并无其他意义。
-
-{{% thirdparty-content %}}
-
-<!--
-### ACI
-
-[Cisco Application Centric Infrastructure](https://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/index.html) offers an integrated overlay and underlay SDN solution that supports containers, virtual machines, and bare metal servers. [ACI](https://www.github.com/noironetworks/aci-containers) provides container networking integration for ACI. An overview of the integration is provided [here](https://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/solution-overview-c22-739493.pdf).
--->
-### ACI
-[Cisco Application Centric Infrastructure](https://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/index.html)
-提供了一个集成覆盖网络和底层 SDN 的解决方案来支持容器、虚拟机和其他裸机服务器。
-[ACI](https://www.github.com/noironetworks/aci-containers) 为 ACI 提供了容器网络集成。
-点击[这里](https://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/solution-overview-c22-739493.pdf)查看概述。
-
-<!--
-### Antrea
-
-Project [Antrea](https://github.com/vmware-tanzu/antrea) is an opensource Kubernetes networking solution intended to be Kubernetes native. It leverages Open vSwitch as the networking data plane. Open vSwitch is a high-performance programmable virtual switch that supports both Linux and Windows. Open vSwitch enables Antrea to implement Kubernetes Network Policies in a high-performance and efficient manner.
-Thanks to the "programmable" characteristic of Open vSwitch, Antrea is able to implement an extensive set of networking and security features and services on top of Open vSwitch.
--->
-### Antrea
-
-[Antrea](https://github.com/vmware-tanzu/antrea) 项目是一个开源的联网解决方案，旨在成为
-Kubernetes 原生的网络解决方案。它利用 Open vSwitch 作为网络数据平面。
-Open vSwitch 是一个高性能可编程的虚拟交换机，支持 Linux 和 Windows 平台。
-Open vSwitch 使 Antrea 能够以高性能和高效的方式实现 Kubernetes 的网络策略。
-借助 Open vSwitch 可编程的特性，Antrea 能够在 Open vSwitch 之上实现广泛的联网、安全功能和服务。
-
-<!--
-### AWS VPC CNI for Kubernetes
-
-The [AWS VPC CNI](https://github.com/aws/amazon-vpc-cni-k8s) offers integrated AWS Virtual Private Cloud (VPC) networking for Kubernetes clusters. This CNI plugin offers high throughput and availability, low latency, and minimal network jitter. Additionally, users can apply existing AWS VPC networking and security best practices for building Kubernetes clusters. This includes the ability to use VPC flow logs, VPC routing policies, and security groups for network traffic isolation.
-
-Using this CNI plugin allows Kubernetes pods to have the same IP address inside the pod as they do on the VPC network. The CNI allocates AWS Elastic Networking Interfaces (ENIs) to each Kubernetes node and using the secondary IP range from each ENI for pods on the node. The CNI includes controls for pre-allocation of ENIs and IP addresses for fast pod startup times and enables large clusters of up to 2,000 nodes.
-
-Additionally, the CNI can be run alongside [Calico for network policy enforcement](https://docs.aws.amazon.com/eks/latest/userguide/calico.html). The AWS VPC CNI project is open source with [documentation on GitHub](https://github.com/aws/amazon-vpc-cni-k8s).
--->
-### Kubernetes 的 AWS VPC CNI     {#aws-vpc-cni-for-kubernetes}
-
-[AWS VPC CNI](https://github.com/aws/amazon-vpc-cni-k8s) 为 Kubernetes 集群提供了集成的
-AWS 虚拟私有云（VPC）网络。该 CNI 插件提供了高吞吐量和可用性，低延迟以及最小的网络抖动。
-此外，用户可以使用现有的 AWS VPC 网络和安全最佳实践来构建 Kubernetes 集群。
-这包括使用 VPC 流日志、VPC 路由策略和安全组进行网络流量隔离的功能。
-
-使用该 CNI 插件，可使 Kubernetes Pod 拥有与在 VPC 网络上相同的 IP 地址。
-CNI 将 AWS 弹性网络接口（ENI）分配给每个 Kubernetes 节点，并将每个 ENI 的辅助 IP 范围用于该节点上的 Pod。
-CNI 包含用于 ENI 和 IP 地址的预分配的控件，以便加快 Pod 的启动时间，并且能够支持多达 2000 个节点的大型集群。
-
-此外，CNI 可以与
-[用于执行网络策略的 Calico](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) 一起运行。
-AWS VPC CNI 项目是开源的，请查看 [GitHub 上的文档](https://github.com/aws/amazon-vpc-cni-k8s)。
-
-<!--
-### Azure CNI for Kubernetes
-[Azure CNI](https://docs.microsoft.com/en-us/azure/virtual-network/container-networking-overview) is an [open source](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) plugin that integrates Kubernetes Pods with an Azure Virtual Network (also known as VNet) providing network performance at par with VMs. Pods can connect to peered VNet and to on-premises over Express Route or site-to-site VPN and are also directly reachable from these networks. Pods can access Azure services, such as storage and SQL, that are protected by Service Endpoints or Private Link. You can use VNet security policies and routing to filter Pod traffic. The plugin assigns VNet IPs to Pods by utilizing a pool of secondary IPs pre-configured on the Network Interface of a Kubernetes node.
-
-Azure CNI is available natively in the [Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/configure-azure-cni).
--->
-### Kubernetes 的 Azure CNI     {#azure-cni-for-kubernetes}
-
-[Azure CNI](https://docs.microsoft.com/en-us/azure/virtual-network/container-networking-overview)
-是一个[开源插件](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md)，
-将 Kubernetes Pods 和 Azure 虚拟网络（也称为 VNet）集成在一起，可提供与 VM 相当的网络性能。
-Pod 可以通过 Express Route 或者 站点到站点的 VPN 来连接到对等的 VNet，
-也可以从这些网络来直接访问 Pod。Pod 可以访问受服务端点或者受保护链接的 Azure 服务，比如存储和 SQL。
-你可以使用 VNet 安全策略和路由来筛选 Pod 流量。
-该插件通过利用在 Kubernetes 节点的网络接口上预分配的辅助 IP 池将 VNet 分配给 Pod。
-
-Azure CNI 可以在
-[Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/configure-azure-cni) 中获得。
-
-<!--
-### Calico
-
-[Calico](https://projectcalico.docs.tigera.io/about/about-calico/) is an open source networking and network security solution for containers, virtual machines, and native host-based workloads. Calico supports multiple data planes including: a pure Linux eBPF dataplane, a standard Linux networking dataplane, and a Windows HNS dataplane. Calico provides a full networking stack but can also be used in conjunction with [cloud provider CNIs](https://projectcalico.docs.tigera.io/networking/determine-best-networking#calico-compatible-cni-plugins-and-cloud-provider-integrations) to provide network policy enforcement.
--->
-### Calico
-
-[Calico](https://projectcalico.docs.tigera.io/about/about-calico/) 是一个开源的联网及网络安全方案，
-用于基于容器、虚拟机和本地主机的工作负载。
-Calico 支持多个数据面，包括：纯 Linux eBPF 的数据面、标准的 Linux 联网数据面
-以及 Windows HNS 数据面。Calico 在提供完整的联网堆栈的同时，还可与
-[云驱动 CNIs](https://projectcalico.docs.tigera.io/networking/determine-best-networking#calico-compatible-cni-plugins-and-cloud-provider-integrations)
-联合使用，以保证网络策略实施。
-
-<!--
-### Cilium
-
-[Cilium](https://github.com/cilium/cilium) is open source software for
-providing and transparently securing network connectivity between application
-containers. Cilium is L7/HTTP aware and can enforce network policies on L3-L7
-using an identity based security model that is decoupled from network
-addressing, and it can be used in combination with other CNI plugins.
--->
-### Cilium
-
-[Cilium](https://github.com/cilium/cilium) 是一个开源软件，用于提供并透明保护应用容器间的网络连接。
-Cilium 支持 L7/HTTP，可以在 L3-L7 上通过使用与网络分离的基于身份的安全模型寻址来实施网络策略，
-并且可以与其他 CNI 插件结合使用。
-
-<!--
-### CNI-Genie from Huawei
-
-[CNI-Genie](https://github.com/cni-genie/CNI-Genie) is a CNI plugin that enables Kubernetes to [simultaneously have access to different implementations](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables) of the [Kubernetes network model](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model) in runtime. This includes any implementation that runs as a [CNI plugin](https://github.com/containernetworking/cni#3rd-party-plugins), such as [Flannel](https://github.com/flannel-io/flannel#flannel), [Calico](https://projectcalico.docs.tigera.io/about/about-calico/), [Weave-net](https://www.weave.works/oss/net/).
-
-CNI-Genie also supports [assigning multiple IP addresses to a pod](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-ips/README.md#feature-2-extension-cni-genie-multiple-ip-addresses-per-pod), each from a different CNI plugin.
--->
-### 华为的 CNI-Genie    {#cni-genie-from-huawei}
-
-[CNI-Genie](https://github.com/cni-genie/CNI-Genie) 是一个 CNI 插件，
-可以让 Kubernetes 在运行时使用不同的[网络模型](#the-kubernetes-network-model)的
-[实现同时被访问](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables)。
-这包括以
-[CNI 插件](https://github.com/containernetworking/cni#3rd-party-plugins)运行的任何实现，比如
-[Flannel](https://github.com/flannel-io/flannel#flannel)、
-[Calico](https://projectcalico.docs.tigera.io/about/about-calico/)、
-[Weave-net](https://www.weave.works/oss/net/)。
-
-CNI-Genie 还支持[将多个 IP 地址分配给 Pod](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-ips/README.md#feature-2-extension-cni-genie-multiple-ip-addresses-per-pod)，
-每个都来自不同的 CNI 插件。
-
-<!--
-### cni-ipvlan-vpc-k8s
-[cni-ipvlan-vpc-k8s](https://github.com/lyft/cni-ipvlan-vpc-k8s) contains a set
-of CNI and IPAM plugins to provide a simple, host-local, low latency, high
-throughput, and compliant networking stack for Kubernetes within Amazon Virtual
-Private Cloud (VPC) environments by making use of Amazon Elastic Network
-Interfaces (ENI) and binding AWS-managed IPs into Pods using the Linux kernel's
-IPvlan driver in L2 mode.
-
-The plugins are designed to be straightforward to configure and deploy within a
-VPC. Kubelets boot and then self-configure and scale their IP usage as needed
-without requiring the often recommended complexities of administering overlay
-networks, BGP, disabling source/destination checks, or adjusting VPC route
-tables to provide per-instance subnets to each host (which is limited to 50-100
-entries per VPC). In short, cni-ipvlan-vpc-k8s significantly reduces the
-network complexity required to deploy Kubernetes at scale within AWS.
--->
-### cni-ipvlan-vpc-k8s
-
-[cni-ipvlan-vpc-k8s](https://github.com/lyft/cni-ipvlan-vpc-k8s)
-包含了一组 CNI 和 IPAM 插件来提供一个简单的、本地主机、低延迟、高吞吐量
-以及通过使用 Amazon 弹性网络接口（ENI）并使用 Linux 内核的 IPv2 驱动程序
-以 L2 模式将 AWS 管理的 IP 绑定到 Pod 中，
-在 Amazon Virtual Private Cloud（VPC）环境中为 Kubernetes 兼容的网络堆栈。
-
-这些插件旨在直接在 VPC 中进行配置和部署，Kubelets 先启动，
-然后根据需要进行自我配置和扩展它们的 IP 使用率，而无需经常建议复杂的管理
-覆盖网络、BGP、禁用源/目标检查或调整 VPC 路由表以向每个主机提供每个实例子网的
-复杂性（每个 VPC 限制为50-100个条目）。
-简而言之，cni-ipvlan-vpc-k8s 大大降低了在 AWS 中大规模部署 Kubernetes 所需的网络复杂性。
-
-<!--
-### Coil
-
-[Coil](https://github.com/cybozu-go/coil) is a CNI plugin designed for ease of integration, providing flexible egress networking.
-Coil operates with a low overhead compared to bare metal, and allows you to define arbitrary egress NAT gateways for external networks.
-
--->
-### Coil
-
-[Coil](https://github.com/cybozu-go/coil) 是一个为易于集成、提供灵活的出站流量网络而设计的 CNI 插件。
-与裸机相比，Coil 的额外操作开销低，并允许针对外部网络的出站流量任意定义 NAT 网关。
-
-<!--
-### Contiv-VPP
-
-[Contiv-VPP](https://contivpp.io/) is a user-space, performance-oriented network plugin for
-Kubernetes, using the [fd.io](https://fd.io/) data plane.
--->
-### Contiv-VPP
-[Contiv-VPP](https://contivpp.io/) 是用于 Kubernetes 的用户空间、面向性能的网络插件，使用 [fd.io](https://fd.io/) 数据平面。
-
-### Contrail / Tungsten Fabric
-
-<!--
-[Contrail](https://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/), based on [Tungsten Fabric](https://tungsten.io), is a truly open, multi-cloud network virtualization and policy management platform. Contrail and Tungsten Fabric are integrated with various orchestration systems such as Kubernetes, OpenShift, OpenStack and Mesos, and provide different isolation modes for virtual machines, containers/pods and bare metal workloads.
--->
-[Contrail](https://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/)
-是基于 [Tungsten Fabric](https://tungsten.io) 的，真正开放的多云网络虚拟化和策略管理平台。
-Contrail 和 Tungsten Fabric 与各种编排系统集成在一起，例如 Kubernetes、OpenShift、OpenStack 和 Mesos，
-并为虚拟机、容器或 Pods 以及裸机工作负载提供了不同的隔离模式。
-
-<!--
-### DANM
-
-[DANM](https://github.com/nokia/danm) is a networking solution for telco workloads running in a Kubernetes cluster. It's built up from the following components:
-
-   * A CNI plugin capable of provisioning IPVLAN interfaces with advanced features
-   * An in-built IPAM module with the capability of managing multiple, cluster-wide, discontinuous L3 networks and provide a dynamic, static, or no IP allocation scheme on-demand
-   * A CNI metaplugin capable of attaching multiple network interfaces to a container, either through its own CNI, or through delegating the job to any of the popular CNI solution like SRI-OV, or Flannel in parallel
-   * A Kubernetes controller capable of centrally managing both VxLAN and VLAN interfaces of all Kubernetes hosts
-   * Another Kubernetes controller extending Kubernetes' Service-based service discovery concept to work over all network interfaces of a Pod
-
-With this toolset DANM is able to provide multiple separated network interfaces, the possibility to use different networking back ends and advanced IPAM features for the pods.
--->
-### DANM
-
-[DANM](https://github.com/nokia/danm) 是一个针对在 Kubernetes 集群中运行的电信工作负载的网络解决方案。
-它由以下几个组件构成：
-
-* 能够配置具有高级功能的 IPVLAN 接口的 CNI 插件
-* 一个内置的 IPAM 模块，能够管理多个、集群内的、不连续的 L3 网络，并按请求提供动态、静态或无 IP 分配方案
-* CNI 元插件能够通过自己的 CNI 或通过将任务授权给其他任何流行的 CNI 解决方案（例如 SRI-OV 或 Flannel）来实现将多个网络接口连接到容器
-* Kubernetes 控制器能够集中管理所有 Kubernetes 主机的 VxLAN 和 VLAN 接口
-* 另一个 Kubernetes 控制器扩展了 Kubernetes 的基于服务的服务发现概念，以在 Pod 的所有网络接口上工作
-
-通过这个工具集，DANM 可以提供多个分离的网络接口，可以为 Pod 使用不同的网络后端和高级 IPAM 功能。
-
-<!--
-### Flannel
-
-[Flannel](https://github.com/flannel-io/flannel#flannel) is a very simple overlay
-network that satisfies the Kubernetes requirements. Many
-people have reported success with Flannel and Kubernetes.
--->
-### Flannel
-
-[Flannel](https://github.com/flannel-io/flannel#flannel) 是一个非常简单的能够满足
-Kubernetes 所需要的覆盖网络。已经有许多人报告了使用 Flannel 和 Kubernetes 的成功案例。
-
-<!--
-### Hybridnet
-
-[Hybridnet](https://github.com/alibaba/hybridnet) is an open source CNI plugin designed for hybrid clouds which provides both overlay and underlay networking for containers in one or more clusters. Overlay and underlay containers can run on the same node and have cluster-wide bidirectional network connectivity.
--->
-### Hybridnet
-
-[Hybridnet](https://github.com/alibaba/hybridnet) 是一个为混合云设计的开源 CNI 插件，
-它为一个或多个集群中的容器提供覆盖和底层网络。Overlay 和 underlay 容器可以在同一个节点上运行，
-并具有集群范围的双向网络连接。
-
-<!--
-### Jaguar
-
-[Jaguar](https://gitlab.com/sdnlab/jaguar) is an open source solution for Kubernetes's network based on OpenDaylight. Jaguar provides overlay network using vxlan and Jaguar CNIPlugin provides one IP address per pod.
-
-### k-vswitch
-
-[k-vswitch](https://github.com/k-vswitch/k-vswitch) is a simple Kubernetes networking plugin based on [Open vSwitch](https://www.openvswitch.org/). It leverages existing functionality in Open vSwitch to provide a robust networking plugin that is easy-to-operate, performant and secure.
--->
-### Jaguar
-
-[Jaguar](https://gitlab.com/sdnlab/jaguar) 是一个基于 OpenDaylight 的 Kubernetes 网络开源解决方案。
-Jaguar 使用 vxlan 提供覆盖网络，而 Jaguar CNIPlugin 为每个 Pod 提供一个 IP 地址。
-
-### k-vswitch
-
-[k-vswitch](https://github.com/k-vswitch/k-vswitch) 是一个基于
-[Open vSwitch](https://www.openvswitch.org/) 的简易 Kubernetes 网络插件。
-它利用 Open vSwitch 中现有的功能来提供强大的网络插件，该插件易于操作，高效且安全。
-
-<!--
-### Knitter
-
-[Knitter](https://github.com/ZTE/Knitter/) is a network solution which supports multiple networking in Kubernetes. It provides the ability of tenant management and network management. Knitter includes a set of end-to-end NFV container networking solutions besides multiple network planes, such as keeping IP address for applications, IP address migration, etc.
-
-### Kube-OVN
-
-[Kube-OVN](https://github.com/alauda/kube-ovn) is an OVN-based kubernetes network fabric for enterprises. With the help of OVN/OVS, it provides some advanced overlay network features like subnet, QoS, static IP allocation, traffic mirroring, gateway, openflow-based network policy and service proxy.
--->
-### Knitter
-
-[Knitter](https://github.com/ZTE/Knitter/) 是一个支持 Kubernetes 中实现多个网络系统的解决方案。
-它提供了租户管理和网络管理的功能。除了多个网络平面外，Knitter 还包括一组端到端的 NFV 容器网络解决方案，
-例如为应用程序保留 IP 地址、IP 地址迁移等。
-
-### Kube-OVN
-
-[Kube-OVN](https://github.com/alauda/kube-ovn) 是一个基于 OVN 的用于企业的 Kubernetes 网络架构。
-借助于 OVN/OVS，它提供了一些高级覆盖网络功能，例如子网、QoS、静态 IP 分配、流量镜像、网关、
-基于 openflow 的网络策略和服务代理。
-
-<!--
-### Kube-router
-
-[Kube-router](https://github.com/cloudnativelabs/kube-router) is a purpose-built networking solution for Kubernetes that aims to provide high performance and operational simplicity. Kube-router provides a Linux [LVS/IPVS](https://www.linuxvirtualserver.org/software/ipvs.html)-based service proxy, a Linux kernel forwarding-based pod-to-pod networking solution with no overlays, and iptables/ipset-based network policy enforcer.
--->
-### Kube-router
-
-[Kube-router](https://github.com/cloudnativelabs/kube-router) 是 Kubernetes 的专用网络解决方案，
-旨在提供高性能和易操作性。
-Kube-router 提供了一个基于 Linux [LVS/IPVS](https://www.linuxvirtualserver.org/software/ipvs.html)
-的服务代理、一个基于 Linux 内核转发的无覆盖 Pod-to-Pod 网络解决方案和基于 iptables/ipset 的网络策略执行器。
-
-<!--
-### L2 networks and linux bridging
-
-If you have a "dumb" L2 network, such as a simple switch in a "bare-metal"
-environment, you should be able to do something similar to the above GCE setup.
-Note that these instructions have only been tried very casually - it seems to
-work, but has not been thoroughly tested.  If you use this technique and
-perfect the process, please let us know.
-
-Follow the "With Linux Bridge devices" section of
-[this very nice tutorial](https://blog.oddbit.com/2014/08/11/four-ways-to-connect-a-docker/) from
-Lars Kellogg-Stedman.
--->
-### L2 networks and linux bridging
-
-如果你具有一个“哑”的 L2 网络，例如“裸机”环境中的简单交换机，则应该能够执行与上述 GCE 设置类似的操作。
-请注意，这些说明仅是非常简单的尝试过-似乎可行，但尚未经过全面测试。
-如果你使用此技术并完善了流程，请告诉我们。
-
-根据 Lars Kellogg-Stedman 的这份非常不错的 “Linux 网桥设备”
-[使用说明](https://blog.oddbit.com/2014/08/11/four-ways-to-connect-a-docker/)来进行操作。
-
-<!--
-### Multus (a Multi Network plugin)
-
-Multus is a Multi CNI plugin to support the Multi Networking feature in Kubernetes using CRD based network objects in Kubernetes.
-
-Multus supports all [reference plugins](https://github.com/containernetworking/plugins) (eg. [Flannel](https://github.com/containernetworking/cni.dev/blob/main/content/plugins/v0.9/meta/flannel.md), [DHCP](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/dhcp), [Macvlan](https://github.com/containernetworking/plugins/tree/master/plugins/main/macvlan)) that implement the CNI specification and 3rd party plugins (eg. [Calico](https://github.com/projectcalico/cni-plugin), [Weave](https://github.com/weaveworks/weave), [Cilium](https://github.com/cilium/cilium), [Contiv](https://github.com/contiv/netplugin)). In addition to it, Multus supports [SRIOV](https://github.com/hustcat/sriov-cni), [DPDK](https://github.com/Intel-Corp/sriov-cni), [OVS-DPDK & VPP](https://github.com/intel/vhost-user-net-plugin) workloads in Kubernetes with both cloud native and NFV based applications in Kubernetes.
--->
-### Multus (a Multi Network plugin)
-
-[Multus](https://github.com/Intel-Corp/multus-cni) 是一个多 CNI 插件，
-使用 Kubernetes 中基于 CRD 的网络对象来支持实现 Kubernetes 多网络系统。
-
-Multus 支持所有[参考插件](https://github.com/containernetworking/plugins)（比如：
-[Flannel](https://github.com/containernetworking/cni.dev/blob/main/content/plugins/v0.9/meta/flannel.md)、
-[DHCP](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/dhcp)、
-[Macvlan](https://github.com/containernetworking/plugins/tree/master/plugins/main/macvlan) ）
-来实现 CNI 规范和第三方插件（比如：
-[Calico](https://github.com/projectcalico/cni-plugin)、
-[Weave](https://github.com/weaveworks/weave)、
-[Cilium](https://github.com/cilium/cilium)、
-[Contiv](https://github.com/contiv/netplugin)）。
-除此之外，Multus 还支持
-[SRIOV](https://github.com/hustcat/sriov-cni)、
-[DPDK](https://github.com/Intel-Corp/sriov-cni)、
-[OVS-DPDK & VPP](https://github.com/intel/vhost-user-net-plugin) 的工作负载，
-以及 Kubernetes 中基于云的本机应用程序和基于 NFV 的应用程序。
-
-<!--
-### OVN4NFV-K8s-Plugin (OVN based CNI controller & plugin)
-
-[OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin) is OVN based CNI controller plugin to provide cloud native based Service function chaining(SFC), Multiple OVN overlay networking, dynamic subnet creation, dynamic creation of virtual networks, VLAN Provider network, Direct provider network and pluggable with other Multi-network plugins, ideal for edge based cloud native workloads in Multi-cluster networking
--->
-### OVN4NFV-K8s-Plugin（基于 OVN 的 CNI 控制器和插件）    {#ovn4nfv-k8s-plugin-ovn-based-cni-controller-plugin}
-
-[OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin) 是基于 OVN 的
-CNI 控制器插件，提供基于云原生的服务功能链 (SFC)、多个 OVN
-覆盖网络、动态子网创建、虚拟网络的动态创建、VLAN Provider 网络、Direct Provider
-网络且可与其他多网络插件组合，非常适合多集群网络中基于边缘的云原生工作负载。
-
-<!--
-### NSX-T
-
-[VMware NSX-T](https://docs.vmware.com/en/VMware-NSX-T/index.html) is a network virtualization and security platform. NSX-T can provide network virtualization for a multi-cloud and multi-hypervisor environment and is focused on emerging application frameworks and architectures that have heterogeneous endpoints and technology stacks. In addition to vSphere hypervisors, these environments include other hypervisors such as KVM, containers, and bare metal.
-
-[NSX-T Container Plug-in (NCP)](https://docs.vmware.com/en/VMware-NSX-T/2.0/nsxt_20_ncp_kubernetes.pdf) provides integration between NSX-T and container orchestrators such as Kubernetes, as well as integration between NSX-T and container-based CaaS/PaaS platforms such as Pivotal Container Service (PKS) and OpenShift.
--->
-### NSX-T
-
-[VMware NSX-T](https://docs.vmware.com/en/VMware-NSX-T/index.html) 是一个网络虚拟化和安全平台。
-NSX-T 可以为多云及多系统管理程序环境提供网络虚拟化，并专注于具有异构端点和技术堆栈的新兴应用程序框架和体系结构。
-除了 vSphere 管理程序之外，这些环境还包括其他虚拟机管理程序，例如 KVM、容器和裸机。
-
-[NSX-T Container Plug-in (NCP)](https://docs.vmware.com/en/VMware-NSX-T/2.0/nsxt_20_ncp_kubernetes.pdf)
-提供了 NSX-T 与容器协调器（例如 Kubernetes）之间的结合，
-以及 NSX-T 与基于容器的 CaaS/PaaS 平台（例如 Pivotal Container Service（PKS）和 OpenShift）之间的集成。
-
-<!--
-### OVN (Open Virtual Networking)
-
-OVN is an opensource network virtualization solution developed by the
-Open vSwitch community.  It lets one create logical switches, logical routers,
-stateful ACLs, load-balancers etc to build different virtual networking
-topologies.  The project has a specific Kubernetes plugin and documentation
-at [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes).
--->
-### OVN（开放式虚拟网络）    {#ovn-open-virtual-networking}
-
-OVN 是一个由 Open vSwitch 社区开发的开源的网络虚拟化解决方案。
-它允许创建逻辑交换器、逻辑路由、状态 ACL、负载均衡等等来建立不同的虚拟网络拓扑。
-该项目在 [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)
-提供特定的 Kubernetes 插件和文档。
-
-<!--
-### Weave Net from Weaveworks
-
-[Weave Net](https://www.weave.works/oss/net/) is a
-resilient and simple to use network for Kubernetes and its hosted applications.
-Weave Net runs as a [CNI plug-in](https://www.weave.works/docs/net/latest/cni-plugin/)
-or stand-alone.  In either version, it doesn't require any configuration or extra code
-to run, and in both cases, the network provides one IP address per pod - as is standard for Kubernetes.
--->
-### Weaveworks 的 Weave Net    {#weave-net-from-weaveworks}
-
-[Weave Net](https://www.weave.works/oss/net/) 为 Kubernetes
-及其托管应用提供的、弹性且易用的网络系统。
-Weave Net 可以作为 [CNI 插件](https://www.weave.works/docs/net/latest/cni-plugin/) 运行或者独立运行。
-在这两种运行方式里，都不需要任何配置或额外的代码即可运行，并且在两种情况下，
-网络都为每个 Pod 提供一个 IP 地址 -- 这是 Kubernetes 的标准配置。
+请参阅[此页面](/zh-cn/docs/concepts/cluster-administration/addons/#networking-and-network-policy)了解
+Kubernetes 支持的网络插件的非详尽列表。
 
 ## {{% heading "whatsnext" %}}