From 8a484aff51fd0333dfe84a572901914d904eec6a Mon Sep 17 00:00:00 2001 From: gavinB-orange Date: Tue, 4 Oct 2016 19:08:22 +0200 Subject: [PATCH] Update minikube.md to cover use behind a web proxy In a corporate environment you need to pass proxy information, and just setting the appropriate environment variables does not work. The code snippet here works for me --- docs/getting-started-guides/minikube.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md index 020fc5e257..1ad16b6d28 100644 --- a/docs/getting-started-guides/minikube.md +++ b/docs/getting-started-guides/minikube.md @@ -99,6 +99,14 @@ Kubectl is now configured to use the cluster. This will build and start a lightweight local cluster, consisting of a master, etcd, Docker and a single node. +If you are behind a web proxy, you will need to pass this information in e.g. via + +``` + +https_proxy= minikube start --docker-env HTTP_PROXY= --docker-env HTTPS_PROXY= --docker-env NO_PROXY=192.168.99.0/24 + +Unfortunately just setting the environment variables will not work. +``` Minikube will also create a "minikube" context, and set it to default in kubectl. To switch back to this context later, run this command: `kubectl config use-context minikube`.