github/multus-cni
1
0
Fork 1
mirror of https://github.com/k8snetworkplumbingwg/multus-cni.git synced 2025-07-05 03:46:15 +00:00
Code Issues Projects Releases Wiki Activity

[docs] Updates the README.md to reflect the need for a default network and removes Flannel reference.

Browse Source
This commit is contained in:
Doug Smith 2019-04-03 19:23:06 -04:00 committed by Doug Smith
parent 9b587c6089
commit 1d4ac10f3d
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -22,11 +22,9 @@ Here's an illustration of the network interfaces attached to a pod, as provision
## Quickstart Installation Guide ## 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. 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](doc/quickstart.md).
Firstly, clone this GitHub repository. We'll apply files to `kubectl` from this repo. 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:
We apply these files as such:
``` ```
$ cat ./images/multus-daemonset.yml | kubectl apply -f - $ cat ./images/multus-daemonset.yml | kubectl apply -f -