DevFW-CICD/ingress-nginx-helm
15
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fixes for minikube usage instructions.

Browse source
This commit is contained in:
Marcin Owsiany 2017-02-03 18:45:51 +01:00
parent a3c8f6c141
commit da9154310e
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/dev/setup.md
View file

@ -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