Merge pull request #220 from porridge/minikube-fixes
Fixes for minikube usage instructions.
This commit is contained in:
commit
b90003abde
1 changed files with 6 additions and 2 deletions
|
@ -49,7 +49,7 @@ NAME STATUS AGE VERSION
|
||||||
a sandboxed local cluster. You will first need to [install](https://github.com/kubernetes/minikube/releases)
|
a sandboxed local cluster. You will first need to [install](https://github.com/kubernetes/minikube/releases)
|
||||||
the minikube binary, then bring up a cluster
|
the minikube binary, then bring up a cluster
|
||||||
```console
|
```console
|
||||||
$ minikube up
|
$ minikube start
|
||||||
```
|
```
|
||||||
|
|
||||||
Check for Ready nodes
|
Check for Ready nodes
|
||||||
|
@ -71,12 +71,16 @@ $ minikube addons list
|
||||||
If this list already contains the ingress controller, you don't need to
|
If this list already contains the ingress controller, you don't need to
|
||||||
redeploy it. If the addon controller is disabled, you can enable it with
|
redeploy it. If the addon controller is disabled, you can enable it with
|
||||||
```console
|
```console
|
||||||
$ minikube enable addons ingress
|
$ minikube addons enable ingress
|
||||||
```
|
```
|
||||||
|
|
||||||
If the list *does not* contain the ingress controller, you can either update
|
If the list *does not* contain the ingress controller, you can either update
|
||||||
minikube, or deploy it yourself as shown in the next section.
|
minikube, or deploy it yourself as shown in the next section.
|
||||||
|
|
||||||
|
You may want to consider [using the VM's docker
|
||||||
|
daemon](https://github.com/kubernetes/minikube/blob/master/README.md#reusing-the-docker-daemon)
|
||||||
|
when developing.
|
||||||
|
|
||||||
## Deploy the ingress controller
|
## Deploy the ingress controller
|
||||||
|
|
||||||
You can deploy an ingress controller on the cluster setup in the previous step
|
You can deploy an ingress controller on the cluster setup in the previous step
|
||||||
|
|
Loading…
Reference in a new issue