I have been trying to install minikube for two days now. I have run into issue after issue. This one has me stumped.

• install minikube on windows 10
• Docker has been running with hyperv for months
• followed windows using choco ignoring everything with hyperv install.

W0107 08:23:27.485052 3337 common.go:77] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta1". Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.

From what i understand there is a new config. that i need to migrate to. to do that i need to use kubeadm but I haven't been able to find any information on where to find these files or how to do the migration. Here is what i have tried.

From an elevated command prompt i ran:

• minikube ssh

Then i found kubeadm in the following directory.

• cd /var/lib/minikube/binaries/v1.17.0

where by i started throwing some random commands at it in hopes of some help

$ ./kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:17:50Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}


$ ./kubeadm config view
failed to load admin kubeconfig: open /home/docker/.kube/config: no such file or directory
To see the stack trace of this error execute with --v=5 or higher

$ ./kubeadm init --config defaults
unable to read config from "defaults" : open defaults: no such file or directory
To see the stack trace of this error execute with --v=5 or higher

As the error message said to run this i gave that a go. That didnt work either

$ ./kubeadm config migrate --old-config old.yaml --new-config new.yaml
open old.yaml: no such file or directory
To see the stack trace of this error execute with --v=5 or higher

After digging around in the logs i found that it was trying to load the following config file so i tried to load that as the old one in hopes it was smart enough to make its own new one.

./kubeadm config migrate --old-config /var/tmp/minikube/kubeadm.yaml --new-config new.yaml
open /var/tmp/minikube/kubeadm.yaml: permission denied 
To see the stack trace of this error execute with --v=5 or higher

Ok then lets check the permissions on the file

$ ls -la /var/tmp/minikube/kubeadm.yaml
-rw-r----- 1 root root 1156 Jan  1  0001 /var/tmp/minikube/kubeadm.yaml

Well that's not good let's try to update it

$ chmod u=r /var/tmp/minikube/kubeadm.yaml
chmod: changing permissions of '/var/tmp/minikube/kubeadm.yaml': Operation not 
 permitted

ok

$ sudu chmod u=r /var/tmp/minikube/kubeadm.yaml
-bash: sudu: command not found

edit sudo

 $ sudo chmod u=r /var/tmp/minikube/kubeadm.yaml 
 $ ls -la /var/tmp/minikube/kubeadm.yaml
 -r--r----- 1 root root 1156 Jan  1  0001 /var/tmp/minikube/kubeadm.yaml

update 777

$ sudo chmod 777 /var/tmp/minikube/kubeadm.yaml
$ ls -la /var/tmp/minikube/kubeadm.yaml
-rwxrwxrwx 1 root root 1156 Jan  1  0001 /var/tmp/minikube/kubeadm.yaml
fig new.yamlconfig migrate --old-config /var/tmp/minikube/kubeadm.yaml --new-conf
W0107 13:19:23.298409    4361 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0107 13:19:23.298437    4361 validation.go:28] Cannot validate kubelet config - no validator is available
failed to write the new configuration to the file "new.yaml": open new.yaml: permission denied
To see the stack trace of this error execute with --v=5 or higher

Still no dice. this appears to be a very limited bash shell.

have a file

Ok thanks to some chmod 777's i know have a file but what do i do with it?

./kubeadm config migrate --old-config /var/tmp/minikube/kubeadm.yaml --new-config /home/docker/new.yaml
W0107 13:22:21.615314    6352 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0107 13:22:21.615375    6352 validation.go:28] Cannot validate kubelet config - no validator is available

There seems to be little or no documentation on how to deal with this I have cross posted the issue on the forum. #6227 any help would be greatly appreciated. I have tried to remove minikube and add it again with the same results.

current status

sudo chmod 777 /var/tmp/minikube/kubeadm.yaml
ls -la /var/tmp/minikube/kubeadm.yaml
cd /var/lib/minikube/binaries/v1.17.0
./kubeadm config migrate --old-config /var/tmp/minikube/kubeadm.yaml --new-config /home/docker/new.yaml
sudo chmod 777 /var/tmp/minikube 
mv /var/tmp/minikube/kubeadm.yaml /var/tmp/minikube/kubeadmold.yaml
mv /home/docker/new.yaml /var/tmp/minikube/kubeadm.yaml

minikube start --vm-driver=hyperv --v=7 --alsologtostderr

No change same error message.

1.16.0

C:\Windows\system32>minikube start --vm-driver=hyperv --kubernetes-version=1.16.0
* minikube v1.6.0 on Microsoft Windows 10 Pro 10.0.18363 Build 18363
* Selecting 'hyperv' driver from user configuration (alternates: [])
* Creating hyperv VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
! Unable to verify SSH connectivity: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address. Will retry...
X minikube is unable to connect to the VM: dial tcp: address fe80::215:5dff:fe37:c505:22: too many colons in address

This is likely due to one of two reasons:

- VPN or firewall interference
- hyperv network configuration issue

Suggested workarounds:

- Disable your local VPN or firewall software
- Configure your local VPN or firewall to allow access to fe80::215:5dff:fe37:c505
- Restart or reinstall hyperv
- Use an alternative --vm-driver