Skip to content
No description or website provided.
Branch: master
Clone or download
Permalink
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 add kubelet client for Pod resource info Mar 22, 2019
doc changes sleep in docs to example that uses a trap INT Jun 10, 2019
examples changes sleep in docs to example that uses a trap INT Jun 10, 2019
images Add help text for '--cni-version' Jun 21, 2019
k8sclient add kubelet client for Pod resource info Mar 22, 2019
kubeletclient add kubelet client for Pod resource info Mar 22, 2019
logging Add 'verbose' option to logging minimum information (#275) Mar 7, 2019
multus CNIVersion fix for conflist May 30, 2019
testing Caches all pod delegates json for pods deletion without k8s info Mar 7, 2019
types add test cases for device id assignment May 16, 2019
vendor Revert vendor directory to support old golang (GOPATH mode) Jun 24, 2019
.gitignore Add .gitignore file Dec 3, 2018
.goreleaser.yml Change .goreleaser.yml to support go module build Jun 24, 2019
.travis.yml Revert vendor directory to support old golang (GOPATH mode) Jun 24, 2019
CONTRIBUTING.md Update CONTRIBUTING.md Sep 26, 2017
Dockerfile [dockerfile] Adds Dockerfile.rhel for OpenShift build Dec 6, 2018
Dockerfile.openshift [dockerfile] Updates Dockerfile for OpenShift-style build Jan 7, 2019
LICENSE Initial commit Dec 13, 2016
README.md [docs] Updates the README.md to reflect the need for a default networ… May 16, 2019
build Change .goreleaser.yml to support go module build Jun 24, 2019
go.mod Migrate go modules from glide Jun 24, 2019
go.sum Migrate go modules from glide Jun 24, 2019
test.sh Change .goreleaser.yml to support go module build Jun 24, 2019

README.md

Multus-CNI

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).

multus-pod-image

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.