minikube: fresh start: waiting for component=kube-apiserver: timed out waiting for the condition

I found a related issue that said to turn off your VPN, especially if you use Cisco AnyConnect, and restart your computer. That cleared up this issue for me.

Had a same issue on mac 10.13.6, minikube version: v0.35.0, VirtualBox version 5.1.18…

😄 minikube v0.35.0 on darwin (amd64) 💡 Tip: Use ‘minikube start -p <name>’ to create a new cluster, or ‘minikube delete’ to delete this one. 🔄 Restarting existing virtualbox VM for “minikube” … ⌛ Waiting for SSH access … 📶 “minikube” IP address is 192.168.99.112 🐳 Configuring Docker as the container runtime … ✨ Preparing Kubernetes environment … 🚜 Pulling images required by Kubernetes v1.13.4 … 🔄 Relaunching Kubernetes v1.13.4 using kubeadm … ⌛ Waiting for pods: apiserver

…stop and delete minikube and rm -rf ~/.kube and ~/.minikube, no luck. But I have reinstall the virutalbox 5.1 to virtualbox 6. All sorted.

brew cask uninstall --force virtualbox; 
brew cask install virtualbox
minikube start

😄 minikube v0.35.0 on darwin (amd64) 🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) … 💿 Downloading Minikube ISO … 184.42 MB / 184.42 MB [============================================] 100.00% 0s 📶 “minikube” IP address is 192.168.99.114 🐳 Configuring Docker as the container runtime … ✨ Preparing Kubernetes environment … 💾 Downloading kubelet v1.13.4 💾 Downloading kubeadm v1.13.4 🚜 Pulling images required by Kubernetes v1.13.4 … 🚀 Launching Kubernetes v1.13.4 using kubeadm … ⌛ Waiting for pods: apiserver proxy etcd scheduler controller addon-manager dns 🔑 Configuring cluster permissions … 🤔 Verifying component health … 💗 kubectl is now configured to use “minikube” 🏄 Done! Thank you for using minikube!

same as me. SystemL macOS: 10.14.3 minikube version: v.0.35.0 kubectl version: Client Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.4”, GitCommit:“c27b913fddd1a6c480c229191a087698aa92f0b1”, GitTreeState:“clean”, BuildDate:“2019-03-01T23:34:27Z”, GoVersion:“go1.12”, Compiler:“gc”, Platform:“darwin/amd64”}

$ minikube start 😄 minikube v0.35.0 on darwin (amd64) 🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) … 💿 Downloading Minikube ISO … 184.42 MB / 184.42 MB [============================================] 100.00% 0s 📶 “minikube” IP address is 192.168.99.104 🐳 Configuring Docker as the container runtime … ✨ Preparing Kubernetes environment … 💾 Downloading kubelet v1.13.4 💾 Downloading kubeadm v1.13.4 🚜 Pulling images required by Kubernetes v1.13.4 … 🚀 Launching Kubernetes v1.13.4 using kubeadm … ⌛ Waiting for pods: apiserver

I think it is the issue v0.35.0, please follow the steps below to stop and purge it and download lower version v0.22.3, it works ok.

Waiting for pods: apiserver^Z [7]+ Stopped minikube start $ minikube stop ✋ Stopping “minikube” in virtualbox … 🛑 “minikube” stopped. $ minikube delete 🔥 Deleting “minikube” from virtualbox … 💔 The “minikube” cluster has been deleted. $ brew cask uninstall minikube; ==> Uninstalling Cask minikube ==> Unlinking Binary ‘/usr/local/bin/minikube’. ==> Purging files for version 0.35.0 of Cask minikube $ curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.22.3/minikube-darwin-amd64 && chmod +x minikube % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 73.8M 100 73.8M 0 0 11.8M 0 0:00:06 0:00:06 --:–:-- 12.9M $ sudo mv minikube /usr/local/bin$ rm -rf ~/.minikube ~/.kube; $ minikube start There is a newer version of minikube available (v0.35.0). Download it here: https://github.com/kubernetes/minikube/releases/tag/v0.35.0

To disable this notification, run the following: minikube config set WantUpdateNotification false Starting local Kubernetes v1.7.5 cluster… Starting VM… Downloading Minikube ISO 139.09 MB / 139.09 MB [============================================] 100.00% 0s Getting VM IP address… Moving files into cluster… Setting up certs… Connecting to cluster… Setting up kubeconfig… Starting cluster components… Kubectl is now configured to use the cluster.

same as me. System: macOS 10.14.2 minikube version: v0.35.0 kubectl: Client Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.4”, GitCommit:“c27b913fddd1a6c480c229191a087698aa92f0b1”, GitTreeState:“clean”, BuildDate:“2019-03-01T23:34:27Z”, GoVersion:“go1.12”, Compiler:“gc”, Platform:“darwin/amd64”}

I also faced the same problem and it caused after using/connecting Cisco AnyConnect VPN. Similar networking issue I have seen earlier as well with Virtualbox VM networks.

So basically when we disconnect the VPN it removes the existing routing for VirtualBox networks. So the solution is ifconfig down & ifconfig for all Virtualbox nets.

I use below function in .bashrc file and run it whenever I face this issue. It works for me on Mac.

function vb()
{
        setopt shwordsplit
        ifs=`VBoxManage list hostonlyifs| grep -w 'Name:'| awk '{print $2}'`
                for i in $ifs
                        do
                                sudo ifconfig $i down && sudo ifconfig $i up
                                echo "Done for $i"
                        done
}

# source ~/.bashrc 
# vb 

Yeah, I too have this problem and I always used to get this below error in my Mac machine.

Fatal error: Error getting controller pod for port-forwarding

So I always run below commands. (provided that you have virtualbox installed)

minikube delete
minikube start

If you run into this:

• If your minikube output mentions anything about HTTP_PROXY or HTTPS_PROXY, this error likely means that your NO_PROXY environment variable is misconfigured. Please see: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md

• If not, please attach the output of minikube logs. Otherwise this will be impossible to debug.

Thanks!

Same here System maxOS: 10.14.3 minikube version: v0.35.0 kubectl version: Client Version: version.Info{Major:“1”, Minor:“12”, GitVersion:“v1.12.2”, GitCommit:“17c77c7898218073f14c8d573582e8d2313dc740”, GitTreeState:“clean”, BuildDate:“2018-10-30T21:39:16Z”, GoVersion:“go1.11.1”, Compiler:“gc”, Platform:“darwin/amd64”} Server Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.4”, GitCommit:“c27b913fddd1a6c480c229191a087698aa92f0b1”, GitTreeState:“clean”, BuildDate:“2019-02-28T13:30:26Z”, GoVersion:“go1.11.5”, Compiler:“gc”, Platform:“linux/amd64”}

$ minikube start

o minikube v0.35.0 on darwin (amd64)

! Ignoring --vm-driver=virtualbox, as the existing “minikube” VM was created using the hyperkit driver. ! To switch drivers, you may create a new VM using minikube start -p <name> --vm-driver=virtualbox ! Alternatively, you may delete the existing VM using minikube delete -p minikube

: Re-using the currently running hyperkit VM for “minikube” … : Waiting for SSH access …

• “minikube” IP address is 192.168.64.16
• Configuring Docker as the container runtime …
• Preparing Kubernetes environment …
• Pulling images required by Kubernetes v1.13.4 … : Relaunching Kubernetes v1.13.4 using kubeadm … : Waiting for pods: apiserver

Confirmed minikube started successfully with cisco Anyconnect on after VB upgrade.

@ENGINEBREATH’s trick worked for me. In my case, the proxy variables were not set, so I could safely omit the --docker-env flag, while starting minikube.

CHANGE_MINIKUBE_NONE_USER=true sudo -E minikube start --vm-driver none 

My suspicion is that your systems network environment is not routing HTTP requests to the VM properly.

If this is happening to you, please add the output of the following commands to help me out:

minikube start <options> --alsologtostderr -v=9

minikube status

minikube logs

minikube ssh docker ps -a

Thank you.

NOTE: If your minikube output mentions anything about Found network options: HTTP_PROXY or HTTPS_PROXY, this error likely means that your NO_PROXY environment variable is misconfigured. Please see: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md

@heidini - can confirm I got a working solution removing Minikube:

sudo rm /usr/bin/minikube sudo minikube stop sudo minikube delete && sudo rm -rf ~/.minikube ~/.kube /etc/kubernetes

Then using v0.34.1:

curl -LO https://storage.googleapis.com/minikube/releases/v0.34.1/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/bin/minikube

Then removed environment proxy:

unset HTTP_PROXY unset HTTPS_PROXY unset NO_PROXY

Then sent proxy details on command:

CHANGE_MINIKUBE_NONE_USER=true sudo -E minikube start --vm-driver none --docker-env HTTP_PROXY=$PROXYDETAILS --docker-env HTTPS_PROXY=$PROXYDETAILS --docker-env NO_PROXY=$PROXYDETAILS

This worked for me!!!

minikube delete minikube start

regards

Same issue occurred with mac using minikube v1.0.0. I tried the possible resolution mentioned in this thread but none worked except updating VB version to the latest (from 5.2.26 to 5.2.28)

I’m also using cisco vpn but I turned it off during starting minikube. Will try with ciscoVPN on to see if it works

I have the same problem no matter which version of minikube used. My environment is behind a proxy and I fixed this by settings a correct NO_PROXY env. … “minikube” IP address is 10.0.2.15 …

so I config

export NO_PROXY=localhost,127.0.0.1,10.0.2.0/24

minikube start