whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update minikube.md to cover use behind a web proxy

Browse Source 
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
This commit is contained in:
gavinB-orange
2016-10-04 19:08:22 +02:00
committed by GitHub
parent 8cf8430ad8
commit 8a484aff51
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/minikube.md
+8
View File
@@ -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. 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=<my proxy> minikube start --docker-env HTTP_PROXY=<my proxy> --docker-env HTTPS_PROXY=<my 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. 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`. To switch back to this context later, run this command: `kubectl config use-context minikube`.