Skip to content
No description or website provided.
Go Shell Dockerfile
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Add issue template for {bug,enhance,support} Nov 6, 2018
checkpoint Improve error/debug message Oct 10, 2019
examples changes sleep in docs to example that uses a trap INT Jun 10, 2019
images Bump daemonset tag to v3.4 (#417) Dec 3, 2019
kubeletclient Improve error/debug message Oct 10, 2019
multus Fix unit test to track on updated error message Nov 15, 2019
netutils Adds cursory unit test for default-route and cleans lint (and one err… Oct 29, 2019
testing Added tests to k8sclient.go (#357) Aug 20, 2019
types Properly uses default-route in annotation to set the gateway. Fixes n… Oct 29, 2019
vendor Update k8s npwg repo name due to its change Oct 29, 2019
.gitignore Removes duplicate NetworkAttachment CRD ref Oct 21, 2019
.goreleaser.yml Change .goreleaser.yml to support go module build Jun 24, 2019
.travis.yml [dockerfile] Use ENV GO111MODULE=off when building from openshift/ori… Sep 2, 2019
Dockerfile Multi architecture image and CI job Jul 29, 2019
Dockerfile.ppc64le Multi architecture image and CI job Jul 29, 2019
LICENSE Initial commit Dec 13, 2016 Added coveralls badge (#363) Aug 23, 2019
go.mod Update k8s npwg repo name due to its change Oct 29, 2019
go.sum Update k8s npwg repo name due to its change Oct 29, 2019 Change .goreleaser.yml to support go module build Jun 24, 2019


multus-cni Logo

Travis CIGo Report CardCoverage Status

Multus CNI enables attaching multiple network interfaces to pods in Kubernetes.

How it works

Multus CNI is a container network interface (CNI) plugin for Kubernetes that enables attaching multiple network interfaces to pods. Typically, in Kubernetes each pod only has one network interface (apart from a loopback) -- with Multus you can create a multi-homed pod that has multiple interfaces. This is accomplished by Multus acting as a "meta-plugin", a CNI plugin that can call multiple other CNI plugins.

Multus CNI follows the Kubernetes Network Custom Resource Definition De-facto Standard to provide a standardized method by which to specify the configurations for additional network interfaces. This standard is put forward by the Kubernetes Network Plumbing Working Group.

Multus is one of the projects in the Baremetal Container Experience kit

Multi-Homed pod

Here's an illustration of the network interfaces attached to a pod, as provisioned by Multus CNI. The diagram shows the pod with three interfaces: eth0, net0 and net1. eth0 connects kubernetes cluster network to connect with kubernetes server/services (e.g. kubernetes api-server, kubelet and so on). net0 and net1 are additional network attachments and connect to other networks by using other CNI plugins (e.g. vlan/vxlan/ptp).


Quickstart Installation Guide

The quickstart installation method for Multus requires that you have first installed a Kubernetes CNI plugin to serve as your pod-to-pod network, which we refer to as your "default network" (a network interface that every pod will be creatd with). Each network attachment created by Multus will be in addition to this default network interface. For more detail on installing a default network CNI plugins, refer to our quick-start guide.

Clone this GitHub repository, we'll apply a daemonset which installs Multus using to kubectl from this repo. From the root directory of the clone, apply the daemonset YAML file:

$ cat ./images/multus-daemonset.yml | kubectl apply -f -

This will configure your systems to be ready to use Multus CNI, but, to get started with adding additional interfaces to your pods, refer to our complete quick-start guide

Additional installation Options

  • Install via daemonset using the quick-start guide, above.
  • Download binaries from release page
  • By Docker image from Docker Hub
  • Or, roll-you-own and build from source

Comprehensive Documentation

Contact Us

For any questions about Multus CNI, feel free to ask a question in #general in the Intel-Corp Slack, or open up a GitHub issue.

You can’t perform that action at this time.