From da9154310e7f5f26c200935fb34d8dd5bcc0b3d2 Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Fri, 3 Feb 2017 18:45:51 +0100 Subject: [PATCH] Fixes for minikube usage instructions. --- docs/dev/setup.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/dev/setup.md b/docs/dev/setup.md index 72bd667be3..b41810e1bd 100644 --- a/docs/dev/setup.md +++ b/docs/dev/setup.md @@ -49,7 +49,7 @@ NAME STATUS AGE VERSION a sandboxed local cluster. You will first need to [install](https://github.com/kubernetes/minikube/releases) the minikube binary, then bring up a cluster ```console -$ minikube up +$ minikube start ``` Check for Ready nodes @@ -71,12 +71,16 @@ $ minikube addons list 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 ```console -$ minikube enable addons ingress +$ minikube addons enable ingress ``` If the list *does not* contain the ingress controller, you can either update 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 You can deploy an ingress controller on the cluster setup in the previous step