Skip to content
Permalink
Browse files

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

…t.md
  • Loading branch information...
aneeshkp committed Jan 30, 2019
1 parent 747d31b commit f229cbe47fdcc7dd646904714d7f20581da24e4d
Showing with 6 additions and 11 deletions.
  1. +0 −7 README.md
  2. +6 −0 doc/quickstart.md
  3. +0 −4 images/README.md
@@ -32,13 +32,6 @@ We apply these files as such:
$ 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)

## Additional installation Options
@@ -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 -
```

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

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:
@@ -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
```
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.

0 comments on commit f229cbe

Please sign in to comment.
You can’t perform that action at this time.