<p>I was just curious if there are known workarounds for the Minikube Vpn issue apart from clean wipe of the minikube from the machine and reinstallation. Minikube works just fine when it is connected to either office network or home network but goes dead when connected to a vpn. When I do a <code>kubectl get pods</code> gives an <code>i/o timeout</code>. I did read couple of git issues in their Issues section but none of the solutions seemed comprehensive.</p>

<p>Using Mac OS Minikube V0.25.Any suggestion is truly appreciated!</p>

<p>There are <a href="https://github.com/kubernetes/minikube/search?q=vpn&amp;type=Issues&amp;utf8=%E2%9C%93" rel="nofollow noreferrer">some issues reported around VPN for minikube</a>.</p>

<p>In particular, <a href="https://github.com/kubernetes/minikube/issues/2344" rel="nofollow noreferrer">issue 2344</a> shows the exact error message:</p>

<pre><code>$kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Unable to connect to the server: Gateway Time-out
</code></pre>

<blockquote>
  <p>Not sure any good solution to correct routing but <a href="https://github.com/robertluwang/docker-hands-on-guide/blob/master/minikube-no-tls-verify.md" rel="nofollow noreferrer">there is remedy for this to disable TLS verification</a>.</p>
</blockquote>

<p>From <a href="https://github.com/kubernetes/minikube/issues/2325#issuecomment-352995998" rel="nofollow noreferrer">issue 2325</a>:</p>

<blockquote>
  <p>On a side node, on Windows 10 1709 update, Hyper-V comes with a build in "Default Switch".<br>
  If use it in <code>minikube start</code>, then everything works in minikube. All Host VPN (I have 2, Cisco Anyconnect and ArraySSL VPN) works inside minikube.</p>
</blockquote>

<p>Some networking settings are suggested in "<a href="https://github.com/kubernetes/minikube/issues/38" rel="nofollow noreferrer">vpn or proxy for easier local development (issue 38)</a>".</p>

<p><a href="https://github.com/kubernetes/minikube/issues/1413" rel="nofollow noreferrer">Issue 1413</a> suggests:</p>

<blockquote>
  <p>In order to remedy VPN issues, it is helpful to specify the hostonly nic used by minikube.<br>
  This way other VMs on that NIC will have no issues talking to each other even when Cisco wrecks the local network. Docker Machine t<a href="https://docs.docker.com/machine/reference/create/" rel="nofollow noreferrer"><code>docker-machine create</code></a>) exposes this property:</p>
</blockquote>

<pre><code>--virtualbox-hostonly-nictype "82540EM"   
</code></pre>

<p>This is not yet available with minikube though.</p>

<blockquote>
  <p>As a workaround, specifying IP addresses in the same CIDR as minikube will set put the VM on the same host only network.<br>
  For example, applying an ip address 192.168.99.XX will use the same host only network that minikube uses with its IP address 192.168.99.10X.</p>
</blockquote>
