minikube: Fix cmd args for alternative runtimes (#12365)

Since minikube v0.33.0 the default CNI config is not being provisioned
by default (https://github.com/kubernetes/minikube/pull/3441). Therefore,
we need to pass `--enable-default-cni` when starting minikube.
pull/12469/head
Martynas Pumputis 2019-01-31 23:55:52 +01:00 committed by Kubernetes Prow Robot
parent 33d851c913
commit 9da045a934
1 changed files with 5 additions and 0 deletions

View File

@ -116,6 +116,7 @@ To use [containerd](https://github.com/containerd/containerd) as the container r
```bash
$ minikube start \
--network-plugin=cni \
--enable-default-cni \
--container-runtime=containerd \
--bootstrapper=kubeadm
```
@ -125,6 +126,7 @@ Or you can use the extended version:
```bash
$ minikube start \
--network-plugin=cni \
--enable-default-cni \
--extra-config=kubelet.container-runtime=remote \
--extra-config=kubelet.container-runtime-endpoint=unix:///run/containerd/containerd.sock \
--extra-config=kubelet.image-service-endpoint=unix:///run/containerd/containerd.sock \
@ -138,6 +140,7 @@ To use [CRI-O](https://github.com/kubernetes-incubator/cri-o) as the container r
```bash
$ minikube start \
--network-plugin=cni \
--enable-default-cni \
--container-runtime=cri-o \
--bootstrapper=kubeadm
```
@ -147,6 +150,7 @@ Or you can use the extended version:
```bash
$ minikube start \
--network-plugin=cni \
--enable-default-cni \
--extra-config=kubelet.container-runtime=remote \
--extra-config=kubelet.container-runtime-endpoint=/var/run/crio.sock \
--extra-config=kubelet.image-service-endpoint=/var/run/crio.sock \
@ -160,6 +164,7 @@ To use [rkt](https://github.com/rkt/rkt) as the container runtime run:
```shell
$ minikube start \
--network-plugin=cni \
--enable-default-cni \
--container-runtime=rkt
```