Skip to content
No description or website provided.
Go Shell Dockerfile
Branch: master
Clone or download
nicklesimba and dougbtv Unit tests and update to quickstart guide (#354)
* Added a test for GetLoggingLevel

* Added up to 96% coverage for checkpoint.go

* Improved coverage of checkpoint.go to 96.4%

* Improved coverage of checkpoint.go to 96.4%

* Adding changes so i will have them saved for my remote fork thingy

* Fixed unit tests in checkpoint_test.go and conf_test.go

* Removed unnecessary comments

* improved conf code coverage by an amount that is greater than 0!

* improved coverage, but line 144 of conf.go needs a look

* Added unit tests to multus and types, also fixed a bug in conf.go

* added label to import types/020 in types.go

* hopefully resolved merge conflicts

* increased code coverage in multus.go and conf.go, also added bug fixes and formatting

* addressed all comments in review

* Updated testing.go with better comments

* changed 'thejohn' to '_not_type' for readability

* added additional unit tests

* added tests to kubeletclient.go

* added more unit tests to k8sclient.go and kubeletclient.go

* Added network status annotations section to quickstart and added more unit tests

* made changes to tests based on code review
Latest commit 9085c84 Aug 5, 2019
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 Removed unnecessary comments Jun 28, 2019
doc Unit tests and update to quickstart guide (#354) Aug 5, 2019
examples changes sleep in docs to example that uses a trap INT Jun 10, 2019
images Increase memory resource in ppc64le case. Jul 31, 2019
k8sclient Unit tests and update to quickstart guide (#354) Aug 5, 2019
kubeletclient Unit tests and update to quickstart guide (#354) Aug 5, 2019
logging Unit tests and update to quickstart guide (#354) Aug 5, 2019
multus Unit tests and update to quickstart guide (#354) Aug 5, 2019
testing Updated testing.go with better comments Jul 26, 2019
types Unit tests and update to quickstart guide (#354) Aug 5, 2019
vendor hopefully resolved merge conflicts Jul 26, 2019
.gitignore Add .gitignore file Dec 3, 2018
.goreleaser.yml Change .goreleaser.yml to support go module build Jun 24, 2019
.travis.yml Multi architecture image and CI job Jul 29, 2019
CONTRIBUTING.md Update CONTRIBUTING.md Sep 26, 2017
Dockerfile Multi architecture image and CI job Jul 29, 2019
Dockerfile.openshift [dockerfile] Updates Dockerfile for OpenShift-style build Jan 7, 2019
Dockerfile.ppc64le Multi architecture image and CI job Jul 29, 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.