Clone or download
mrostecki and s1061123 k8sclient: Add missing error check
Before this change, error returned by `libcni.ConfFiles` was
silently ignored.

Signed-off-by: Michal Rostecki <>
Latest commit f157f42 Nov 27, 2018
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 added checkpoint tests file Oct 10, 2018
deployment/webhook run webhook as a deployment Nov 12, 2018
doc Change the namespace to 'kube-system' Dec 5, 2018
examples CRD: interfaceRequest -> interface (v1 spec conformance) Nov 9, 2018
images [rbac] Tightens down RBAC for clusterrole Nov 1, 2018
k8sclient k8sclient: Add missing error check Dec 6, 2018
logging Add logging message for debug/error Aug 16, 2018
multus [bugfix] Delete all delegates instead of breaking out during deletion… Nov 30, 2018
testing Change pod annotation name to '' Nov 30, 2018
types Fix go vet issue. Dec 6, 2018
vendor Revert "Merge branch 'dev/k8s-deviceid-model' into master" Aug 30, 2018
webhook fix indentation Nov 12, 2018
.gitignore Add .gitignore file Dec 3, 2018
.travis.yml [travis] Updates Travis to build ':snapshot' tagged image on each mer… Nov 19, 2018 Update Sep 26, 2017
Dockerfile [dockerfile] Adds Dockerfile.rhel for OpenShift build Dec 6, 2018
Dockerfile.rhel [dockerfile] Adds Dockerfile.rhel for OpenShift build Dec 6, 2018
LICENSE Initial commit Dec 13, 2016 [docs] Adds additional specific guide, some updates to … Nov 29, 2018
build Following group name changes in github. May 18, 2018
glide.lock adding changing in glide yaml and vendor for network status features Jul 30, 2018
glide.yaml Fix glide.yaml Aug 17, 2018 Update with coveralls job inclusion Aug 18, 2018


multus-cni Logo

Travis CIGo Report Card

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

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" (a network interface that every pod will be created with). 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 -

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.