Multus CNI deployment and basic use of kubernetes multi network card scheme

Multus CNI Deployment and basic use

background

After a container starts , By default Generally, there are only two virtual network interfaces （loopback and eth0）, and loopback The flow rate of will always circulate in the container or the machine , The only thing that really supports the business is eth0, Of course, this can be satisfied for most business scenarios .

however If an application or service needs to be provided externally API Call the service , It also needs to meet its own data synchronization based on distributed features , At this time, the performance of a network card is obviously difficult to meet the requirements of production level , Network traffic delay 、 Blocking becomes a bottleneck in this application .

Based on the above pain points and needs , Container multi network solutions are emerging .k8s There is a specification for multiple network cards ：K8sNetworkPlumbingWG/multi-net-spec. Currently known multi network card schemes ：

k8s Multi network card specification ：K8sNetworkPlumbingWG/multi-net-spec

The multi network developed by Huawei CNI plug-in unit ：Huawei-PaaS/CNI-Genie

Intel Developed multi network CNI plug-in unit ：