From a67f1f1d772251f6e7a495dd9d1adac487e57524 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20Str=C3=B6mberg?= Date: Tue, 19 Feb 2019 15:50:53 -0800 Subject: [PATCH] Update http_proxy.md --- docs/http_proxy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/http_proxy.md b/docs/http_proxy.md index 7538739475..22b30fa09b 100644 --- a/docs/http_proxy.md +++ b/docs/http_proxy.md @@ -6,10 +6,10 @@ minikube requires access to the internet via HTTP, HTTPS, and DNS protocols. If * `HTTPS_PROXY` - The URL to your HTTPS proxy * `NO_PROXY` - A comma-separated list of hosts which should not go through the proxy. -The NO_PROXY variable here is important: Without setting it, minikube may not be able to access resources within the VM. minikube has two important ranges of internal IP's: +The NO_PROXY variable here is important: Without setting it, minikube may not be able to access resources within the VM. minikube uses two IP ranges, which should not go through the proxy: -* *192.168.99.1/24*: Used by the minikube VM. Configurable for some hypervisors via `--host-only-cidr` -* *10.96.0.0/12*: Used by service cluster IP's. Configurable via `--service-cluster-ip-range` +* **192.168.99.1/24**: Used by the minikube VM. Configurable for some hypervisors via `--host-only-cidr` +* **10.96.0.0/12**: Used by service cluster IP's. Configurable via `--service-cluster-ip-range` ## Example Usage