kubernetes - VPN下的Minikube怪异行为

Question

我只是好奇是否有已知的解决方法来解决Minikube Vpn的问题，除了将机器上的minikube擦干净并重新安装。 Minikube在连接到办公室网络或家庭网络时都可以正常工作，但是在连接到VPN时会失效。当我做一个kubectl get pods给出一个i/o timeout。我确实在他们的“问题”部分中阅读了几个git问题，但是没有一个解决方案看起来很全面。

使用Mac OS Minikube V0.25。任何建议都非常感谢!

Answer 1

有some issues reported around VPN for minikube。

特别是，issue 2344显示了确切的错误消息:

$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

Not sure any good solution to correct routing but there is remedy for this to disable TLS verification.

从 issue 2325:

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

在“ vpn or proxy for easier local development (issue 38)”中建议一些网络设置。

Issue 1413建议:

In order to remedy VPN issues, it is helpful to specify the hostonly nic used by minikube.
This way other VMs on that NIC will have no issues talking to each other even when Cisco wrecks the local network. Docker Machine tdocker-machine create) exposes this property:

--virtualbox-hostonly-nictype "82540EM"   

但minikube尚不可用。

As a workaround, specifying IP addresses in the same CIDR as minikube will set put the VM on the same host only network.
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.