From 69f5c69ac3bf7eed42ffb732d11aee373a65b941 Mon Sep 17 00:00:00 2001 From: Martin Zacho Date: Thu, 18 Aug 2022 09:57:29 +0200 Subject: [PATCH] Update content/en/docs/concepts/cluster-administration/networking.md Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- content/en/docs/concepts/cluster-administration/networking.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/concepts/cluster-administration/networking.md b/content/en/docs/concepts/cluster-administration/networking.md index 8cf86e8185..6d2fdd5006 100644 --- a/content/en/docs/concepts/cluster-administration/networking.md +++ b/content/en/docs/concepts/cluster-administration/networking.md @@ -37,7 +37,6 @@ To learn about the Kubernetes networking model, see [here](/docs/concepts/servic 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. See [this page](/docs/concepts/cluster-administration/addons/#networking-and-network-policy) for a non-exhaustive list of networking addons supported by Kubernetes. -imply any preferential status. ## {{% heading "whatsnext" %}}