NO_PROXY doesn't respect addr/range - contrary to documentation

[wayne8l]

For whatever reason, NO_PROXY does not respect an addr/range argument in Ubuntu 16.04. Therefore, 192.168.99.1/24 will not make a no proxy exception for an address in that subnet

In this case, what I found works is to replace it with a specific ip address of the minikube vm in NO_PROXY, which in my case was 192.168.99.100.

Please add this to the documentation, thanks!

[tstromberg]

I assume you mean this document: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md#using-minikube-with-an-http-proxy

Just curious - what error did you see with this, and what version of minikube was it on?

I had assumed when I last changed the doc that NO_PROXY parsing allowed for subnets, it seems like Go's HTTP library should allow for it. I guess not!

[wayne8l]

I was using virtualbox (installed through apt) on Ubuntu 16.04, and issuing http requests through curl and Firefox. My guess is that addr/range in NO_PROXY is not universally implemented.

[wayne8l]

I was on the latest version of minikube, but I think this has nothing to do with minikube.

[wayne8l]

This is not an issue when running minikube, but it is an issue when running kubernetes services through nodeport in minikube when I want to curl in or use a browser.

[tstromberg]

Updated https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md

Thanks for the bug report!