-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Run Minikube on Windows 10 with Hyper - v #2042
Comments
Hi, I tried the command kubectl get pods --all-namespaces. The output is as below
I tried accessing the URL https://192.168.0.111:8443/api/v1/proxy/names%20paces/kube-system/services/kubernetes-dashboard I tried accessing the url https://192.168.0.111:8443 |
Hi,
Thanks a ton |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG
I have created an Hyper - V virtual switch and from the network properties I see that it has Internet access. Now go ahead and create a minikube with this virtual machine. It worked till the end where I could see the VM is configured to work with Kubectl. Then when I check the status using
Minikube status I get the following
Minikube running
cluster stopped
Then I typed the command kubectl cluster-info
Kubernetes master is running at https://192.168.0.110:8443
error: group map[certificates.k8s.io:0xc0823c21c0 extensions:0xc0823c2310 storage.k8s.io:0xc0823c2460 federation:0xc0823
0b810 apps:0xc08230bd50 authorization.k8s.io:0xc08230bf10 batch:0xc0823c2150 componentconfig:0xc0823c2230 policy:0xc0823
c2380 rbac.authorization.k8s.io:0xc0823c23f0 :0xc08230bce0 authentication.k8s.io:0xc08230bdc0 autoscaling:0xc08230bf80]
is already registered
Now when I hit the url https://192.168.0.110:8443 I get the output
Site does not exist
Please provide the following details:
Environment:
Minikube version (use
minikube version
):v0.22.2cat ~/.minikube/machines/minikube/config.json | grep DriverName
): Hyper V (external switch)cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):0.23.4The text was updated successfully, but these errors were encountered: