README_draft_1811
- Multus-cni is CNI plugin, acts as a Multi plugin in Kubernetes and provides the multiple network interface support in a pod
- This project is a reference implementation for Kubernetes Network Custom Resource Definition De-facto Standard. For more information refer Network Plumbing Working Group Agenda
- Multus is one of the projects in the Baremetal Container Experience kit
This is the example pod with multus. The pod has three interface: eth0, net0 and net1. eth0 connects kubernetes cluster network to connect with kubernetes server/services (e.g. kubernetes api-server, kubelets and so on). net0 and net1 are network attachment and connect to other networks with other CNI networks (e.g. vlan/vxlan/ptp).
Multus may be deployed as a Daemonset, and is provided in this guide along with Flannel. Flannel is deployed as a pod-to-pod network that is used as our "default network". Each network attachment is made in addition to this default network.
Firstly, clone this GitHub repository. We'll apply files to kubectl from this repo.
We apply these files as such:
$ cat ./images/{multus-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f -
Please see How to use for the details.
- Get binaries from release page
- Get docker image from Docker Hub
- Build from source
- See Development
For any questions about Multus CNI, please reach out on github issue or feel free to contact the developer @kural in our Intel-Corp Slack