Shulou(Shulou.com)06/01 Report--

This article introduces you how to understand CNI, the content is very detailed, interested friends can use for reference, hope to be helpful to you.

With the network model, how to implement it?

In order to ensure the standardization, expansibility and flexibility of the network scheme, Kubernetes adopts Container Networking Interface (CNI) specification.

CNI is a container network specification proposed by CoreOS, which uses the plug-in (Plugin) model to create a container network stack.

The advantage of CNI is that it supports multiple container runtime, not just Docker. CNI's plug-in model supports third-party plug-ins developed by different organizations and companies, which is very attractive to operators and has the flexibility to choose suitable network solutions.

At present, there are a variety of network schemes that support Kubernetes, such as Flannel, Calico, Canal, Weave Net and so on. Because they all implement the CNI specification, no matter which scheme the user chooses, the network model is the same, that is, each Pod has an independent IP that can communicate directly. The difference lies in the underlying implementation of different schemes, some using VxLAN-based Overlay implementation, some are Underlay, there are differences in performance. Then there is whether or not to support Network Policy.

On how to understand CNI to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.