Skip to content
No description or website provided.
Go Shell Dockerfile
Branch: master
Clone or download

Latest commit

Latest commit 809a16f Jun 4, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Skip docker push action if REPOSITORY_PASS is not set Apr 21, 2020
checkpoint Introduce gopkg.in for go module May 15, 2020
doc Introduce gopkg.in for go module May 15, 2020
e2e Add e2e test with kind in CI pipeline Feb 13, 2020
examples Simplify examples directory May 19, 2020
images Move pre-1.16 Kubernetes assets to a deprecated folder (to later remove) May 8, 2020
k8sclient Add deviceid in clusterNetwork May 28, 2020
kubeletclient Introduce gopkg.in for go module May 15, 2020
logging Unit tests and update to quickstart guide (#354) Aug 5, 2019
multus Add deviceid in clusterNetwork May 28, 2020
netutils Introduce gopkg.in for go module May 15, 2020
testing Logging improvement (UID, net-attach-def) Mar 23, 2020
types Introduce gopkg.in for go module May 15, 2020
vendor Introduce gopkg.in for go module May 15, 2020
.gitignore Removes duplicate NetworkAttachment CRD ref Oct 21, 2019
.goreleaser.yml Fix goreleaser file for build-release error Mar 16, 2020
.travis.yml Fix travis CI Feb 10, 2020
CODE_OF_CONDUCT.md Adds code of conduct Jun 5, 2020
CONTRIBUTING.md Update CONTRIBUTING.md Sep 26, 2017
Dockerfile Updates Dockerfile to golang 1.13 (specifying version) Apr 20, 2020
Dockerfile.arm64 Add Dockerfile for building image on arm64 Mar 19, 2020
Dockerfile.openshift [dockerfile] Use ENV GO111MODULE=off when building from openshift/ori… Sep 2, 2019
Dockerfile.ppc64le Multi architecture image and CI job Jul 29, 2019
LICENSE Initial commit Dec 13, 2016
README.md Added coveralls badge (#363) Aug 23, 2019
build Introduce gopkg.in for go module May 15, 2020
go.mod Introduce gopkg.in for go module May 15, 2020
go.sum Add error message in case of unexpected situation Apr 21, 2020
test.sh Change .goreleaser.yml to support go module build Jun 24, 2019

README.md

Multus-CNI

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

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.