github/multus-cni
1
0
Fork 1
mirror of https://github.com/k8snetworkplumbingwg/multus-cni.git synced 2025-09-01 00:52:37 +00:00
Code Issues Projects Releases Wiki Activity

moved crio details out of the README.md and into the ./docs/quickstart.md

Browse Source
This commit is contained in:
Aneesh Puttur
2019-01-30 09:22:46 -05:00
parent 747d31bb30
commit f229cbe47f
3 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@@ -32,13 +32,6 @@ We apply these files as such:
$ cat ./images/{multus-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f - $ cat ./images/{multus-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f -
``` ```
Note: For crio runtime use multus-crio-daemonset.yml (crio uses /usr/libexec/cni as default path for plugin directory). Before deploying daemonsets,delete all default network plugin configuration files under /etc/cni/net.d
If the runtime is cri-o, then apply these files.
```
$ cat ./images/{multus-crio-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](doc/quickstart.md) 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](doc/quickstart.md)
## Additional installation Options ## Additional installation Options

6
doc/quickstart.md
View File

@@ -27,6 +27,12 @@ We'll apply files to `kubectl` from this repo. The files we're applying here spe
$ cat ./images/{multus-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f - $ cat ./images/{multus-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f -
``` ```
Note: For crio runtime use multus-crio-daemonset.yml (crio uses /usr/libexec/cni as default path for plugin directory). Before deploying daemonsets,delete all default network plugin configuration files under /etc/cni/net.d
If the runtime is cri-o, then apply these files.
```
$ cat ./images/{multus-crio-daemonset.yml,flannel-daemonset.yml} | kubectl apply -f -
```
### Validating your installation ### Validating your installation
Generally, the first step in validating your installation is to look at the `STATUS` field of your nodes, you can check it out by looking at: Generally, the first step in validating your installation is to look at the `STATUS` field of your nodes, you can check it out by looking at:

4
images/README.md
View File

@@ -17,10 +17,6 @@ You may wish to deploy Multus as a daemonset, you can do so by starting with the
``` ```
$ kubectl create -f ./images/multus-daemonset.yml $ kubectl create -f ./images/multus-daemonset.yml
``` ```
Note: For crio runtime use multus-crio-daemonset.yml (crio uses /usr/libexec/cni as default path for plugin directory). Before deploying daemonsets,delete all default network plugin configuration files under /etc/cni/net.d
```
$ kubectl create -f ./images/multus-crio-daemonset.yml
```
Note: The likely best practice here is to build your own image given the Dockerfile, and then push it to your preferred registry, and change the `image` fields in the Daemonset YAML to reference that image. Note: The likely best practice here is to build your own image given the Dockerfile, and then push it to your preferred registry, and change the `image` fields in the Daemonset YAML to reference that image.