Kubernetes 使用Hyper-V的Windows 10 Enterprise上的Minikube connectex问题
我的笔记本电脑配置:带Hyper-V(而非虚拟机箱)的Windows 10 Enterprise 我在学习库伯内特的一些教程,在学习的过程中,我的网络连接中断了一段时间。后来,我重新开始学习,但出现以下错误,无法继续:Kubernetes 使用Hyper-V的Windows 10 Enterprise上的Minikube connectex问题,kubernetes,minikube,Kubernetes,Minikube,我的笔记本电脑配置:带Hyper-V(而非虚拟机箱)的Windows 10 Enterprise 我在学习库伯内特的一些教程,在学习的过程中,我的网络连接中断了一段时间。后来,我重新开始学习,但出现以下错误,无法继续: C:\kubernetes\demo>minikube version minikube version: v1.10.1 commit: 63ab801ac27e5742ae442ce36dff7877dcccb278 C:\kubernetes\demo>kub
C:\kubernetes\demo>minikube version
minikube version: v1.10.1
commit: 63ab801ac27e5742ae442ce36dff7877dcccb278
C:\kubernetes\demo>kubectl version --short
Client Version: v1.18.0
Server Version: v1.18.2
C:\kubernetes\demo>minikube ip
192.168.1.103
C:\kubernetes\demo>kubectl get all
Unable to connect to the server: dial tcp 192.168.1.103:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
另外,通过命令“minikube日志”,我看到:
* E0529 17:56:11.077679 1 reflector.go:205] k8s.io/minikube/vendor/github.com/r2d4/external-storage/lib/controller/controller.go:412: Failed to list *v1.PersistentVolume: Get https://10.96.0.1:443/api/v1/persistentvolumes?resourceVersion=0: dial tcp 10.96.0.1:443: getsockopt: no route to host
* E0529 17:56:11.077719 1 reflector.go:205] k8s.io/minikube/vendor/github.com/r2d4/external-storage/lib/controller/controller.go:411: Failed to list *v1.PersistentVolumeClaim: Get https://10.96.0.1:443/api/v1/persistentvolumeclaims?resourceVersion=0: dial tcp 10.96.0.1:443: getsockopt: no route to host
我确实在谷歌上搜索过这个问题,但最终没有结果
有什么建议吗
编辑1:当网络/互联网发生变化时(例如,当我关闭/打开VPN时),就会发生这种情况(根据我的观察)。拆除和重新安装minikube并非始终可行 我确实运行了下面的命令,到目前为止它工作正常
minikube start --vm-driver hyperv
之前,我运行了下面的命令,并多次遇到问题,正如前面讨论的那样
minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"
在这里,我创建了“主虚拟交换机”,这可能是导致此问题的潜在虚拟交换机