fresh start: waiting for component=kube-apiserver: timed out waiting for the condition #3844
Comments
|
same as me. |
|
Same here, on MacOS as well. On a side note, I am running behind a proxy (setting it with --docker-env). Could that be related? |
|
same as me. $ minikube start |
|
Same here $ 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. : Re-using the currently running hyperkit VM for "minikube" ...
|
|
Same Here |
|
Hi there - I too am hitting the same error! System: Linux CentOS $ CHANGE_MINIKUBE_NONE_USER=true sudo -E minikube start --vm-driver=none
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one. |
|
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 To disable this notification, run the following: |
|
@heidini - can confirm I got a working solution removing Minikube:
Then using v0.34.1:
Then removed environment proxy:
Then sent proxy details on command:
|
|
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:
Thank you. NOTE: If your minikube output mentions anything about |
tstromberg
added
area/networking
tstromberg
changed the title
|
@ENGINEBREATH , thanks a log, I just tried v0.34.1, it also works on my Mac: To download the the version for mac, please use the following command: |
|
Same here on my mac. |
|
I am on Ubuntu 18.04, I have a similar problem with extra-config
Got this
|
|
@MilenkoM - Chances are your extra flags are breaking the restart of apiserver. Please open a new issue with the output of |
tstromberg
changed the title
|
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) ....stop and delete minikube and rm -rf ~/.kube and ~/.minikube, no luck. 😄 minikube v0.35.0 on darwin (amd64) |
|
@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. |
|
I resolved this with the following: Note that the I'm running minikube on manjaro (arch): I believe that the doc here: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md The results are as you'd expect: |
|
Hi there,
And I'm getting this error: And keep waiting until raise the error: 😄 minikube v1.0.0 on darwin (amd64) 💣 Error starting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: |
|
If you run into this:
Thanks! |
|
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. |
|
Having the same problem
✘ 09:09:33 ~ $ minikube delete ✔ 11:38:03 ~ $ minikube start --host-only-cidr "192.168.5.1/24" 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: ✘ 11:51:16 ~ $ minikube version ✔ 11:53:58 ~ $ |
|
@coolteddy thanks a lot |
|
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.
So I always run below commands. (provided that you have virtualbox installed) |
I did all the hard things first but a restart after having used CiscoVPN a couple weeks ago is what cleared the minikube startup problem I was having ("Waiting for SSH access ..."). This seems like a significant clue to the problem... Maybe my Mac's networking state was in an unexpected configuration as a result of running CiscoVPN. Other's have reported success after doing upgrades and downgrades but I'm wondering if they did not realize that they did other things that might have also had an effect on curing their problem... like rebooting or sleeping (I do neither). |
|
I have the same problem no matter which version of minikube used. so I config export NO_PROXY=localhost,127.0.0.1,10.0.2.0/24 minikube start |
|
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 |
|
Confirmed minikube started successfully with cisco Anyconnect on after VB upgrade. |
|
Same issue. macOS Mojave 10.14.4 (18E226) After stuck in |
|
This worked for me!!! minikube delete regards |
tstromberg
added
co/apiserver
tstromberg
changed the title
|
I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube, and if the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience! |
|
Same issue with 1.1.1 |
|
Same issue here with 1.1.1 on macOS Mojave 10.14.4 |
|
same with 1.1.1 macOS Mojave 10.14.5 virtualbox: 5.2.30r130521 |
|
Same with 1.1.1 macOS Mojave 10.14.5 VirtualBox:Version 6.0.8 r130520 (Qt5.6.3) kubectl delete |
bash: setopt: command not found When I try to run it |
Is it on Mac OSX? |
and others
minikube version: v0.35.0
kubectl client version v1.10.11
How to replicate the error:
=================
(after "minikube delete", "del /f .minikube" and "del /f .kube"...)
C:\WINDOWS\system32>minikube start
o minikube v0.35.0 on windows (amd64)
> Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
- "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 ...
- Launching Kubernetes v1.13.4 using kubeadm ...
: Waiting for pods: apiserver! Error starting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition
* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
- https://github.com/kubernetes/minikube/issues/new
[minikubes_problem.zip](https://github.com/kubernetes/minikube/files/2949942/minikubes_problem.zip)
The text was updated successfully, but these errors were encountered: