minikube: kube-proxy configmap update: timed out (unknown root cause)

I had this error when upgrading from 0.25 to 0.26.1. Simply performing minikube delete and then re-creating the cluster fixed the issue for me.

I had the exact same error message, as suggested by @hungvnvnext I downgraded minikube formula using homebrew and was able to start minikube.

maybe downgrading helps you until someone with minikube knowledge can review this issue.

my OS: macOS High Sierra 10.13.3 VM: vmware fusion

$ brew cask edit minikube

This is how it should look for minikube version 0.25.2

cask 'minikube' do
  version '0.25.2'
  sha256 'dc5b00c4a06e8160bd607732c9a2294598d803716e353293b4463cc2c9539eec'

  # storage.googleapis.com/minikube was verified as official when first introduced to the cask
  url "https://storage.googleapis.com/minikube/releases/v#{version}/minikube-darwin-amd64"
  appcast 'https://github.com/kubernetes/minikube/releases.atom',
          checkpoint: 'ce48a5c392fb7b35a106ae78ca225bc3c01e4afcb99d96957d3f8d0dcf55d910'
  name 'Minikube'
  homepage 'https://github.com/kubernetes/minikube'

  depends_on formula: 'kubernetes-cli'
  container type: :naked

  binary 'minikube-darwin-amd64', target: 'minikube'

  zap trash: '~/.minikube'
end

Re install minikube

$ minikube delete
$ sudo rm -rf ~/.minikube
$ brew cask reinstall minikube
$ minikube --vm-driver=vmwarefusion start

I my case I did minikube delete and minikube start and it worked. In the first start try, I had a internet connection problem and pressed ctrl+c.

minikube delete followed by minikube start didn’t work for me. Same or similar errors to what is reported here on version 0.26.1

Release v0.25.2 works fine.

minikube delete && minikube start worked for me on macOS.

I am confirming the solution of @julianduque for macOS kubernauts. As a summary:

brew cask reinstall minikube
minikube delete
minikube start

Before applying this solution

After applying this solution

Let’s continue kubing!

I had the same issue – Found out that my local firewall software (Little Snitch) blocked some minikube-related requests in the background (Silent Mode was active), which lead to the timeout on my Mac.

minikube delete && minikube restart works for me. minikube version: v0.32.0 macOS version: Mojave 10.14.2 Virtualbox version: 6.0.2

issue was with v0.28.0

minikube delete
minikube start

solved the problem.

minikube version: v0.26.1 Windows 10 Enterprise Hyper-V

Was having the same issue with starting a cluster. Did the following and it worked.

minikube delete minikube start --kubernetes-version="v1.10.0" --vm-driver="hyperv"

same issue on v0.26.0 on Mac High Sierra 10.13.4 base on vmware fusion 10.

Happened on version v0.30.0 MacOS Mojave solved by minikube delete && minikube start

Just

minikube delete minikube start

worked for me !!! Thanks

minikube delete
minikube start

The above worked for me.

Same here on Mac. #minikube version minikube version: v0.26.1

minikube logs – Logs begin at Tue 2018-04-24 11:31:00 UTC, end at Tue 2018-04-24 11:31:16 UTC. – Apr 24 11:31:11 minikube systemd[1]: /etc/systemd/system/kubelet.service.d/10-kubeadm.conf:7: Unknown lvalue ‘Wants’ in section ‘Install’ Apr 24 11:31:11 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent. Apr 24 11:31:11 minikube kubelet[5448]: Flag --client-ca-file has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --fail-swap-on has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --cluster-domain has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --authorization-mode has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --cluster-dns has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --cadvisor-port has been deprecated, The default will change to 0 (disabled) in 1.12, and the cadvisor port will be removed entirely in 1.13 Apr 24 11:31:11 minikube kubelet[5448]: Flag --pod-manifest-path has been deprecated, This parameter should be set via the config file specified by the Kubelet’s --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Apr 24 11:31:11 minikube kubelet[5448]: Flag --allow-privileged has been deprecated, will be removed in a future version Apr 24 11:31:11 minikube kubelet[5448]: I0424 11:31:11.662881 5448 feature_gate.go:226] feature gates: &{{} map[]} Apr 24 11:31:11 minikube kubelet[5448]: W0424 11:31:11.678500 5448 hostport_manager.go:68] The binary conntrack is not installed, this can cause failures in network connection cleanup. Apr 24 11:31:11 minikube kubelet[5448]: I0424 11:31:11.678821 5448 server.go:376] Version: v1.10.0 Apr 24 11:31:11 minikube kubelet[5448]: I0424 11:31:11.679075 5448 feature_gate.go:226] feature gates: &{{} map[]} Apr 24 11:31:11 minikube kubelet[5448]: I0424 11:31:11.679362 5448 plugins.go:89] No cloud provider specified. Apr 24 11:31:11 minikube kubelet[5448]: F0424 11:31:11.679562 5448 server.go:233] failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directory Apr 24 11:31:11 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a Apr 24 11:31:11 minikube systemd[1]: kubelet.service: Unit entered failed state. Apr 24 11:31:11 minikube systemd[1]: kubelet.service: Failed with result ‘exit-code’.

I also face the same issue it’s occurred because of uncomplete installation or setup of minikube in my case minikube version: v0.30.0 i solve this issue by using:

minikube delete minikube start

and done it work’s

Same here on Linux (CentOS Linux release 7.4.1708 (Core) ).

Linux 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

minikube version: v0.27.0

Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...

E0524 17:22:21.606627   28661 start.go:281] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

But when I do the same operating on another Fedora 28 Linux, all things work fined.

Got the same issue on v0.26.1 on Mac 10.13.3. Downgrade minikube to 0.25.2 and it seems to work fine.

I have the same issue, although oddly enough the cluster seems to have started… I can access it via kubectl, deploy to it, etc.

I had the same issue with OS: Mac OSX High Sierra v10.13.6 minikube version: v0.28.2 kubectl version 1.10

I did a minikube delete && minikube start and it resolved the issue.

deleting and re-installing worked for with minikube version: v0.27.0

minikube delete
rm -rf ~/.minikube
brew reinstall kubectl

minikube start --vm-driver=xhyve

Same here on Mac. Minikube version v0.26.1

I suspect VPN issues in general for this error, but do you mind including the output of “minikube logs”?

Also, please provide your VM driver and operating system info. Thanks! This may be a dupe of #3031

As a workarround we can start minikube with bootstrapper localkube, default is kubeadm.

WARNING: The localkube bootstrapper is now deprecated and support for it

minikube start --bootstrapper=localkube

minikube delete minikube start

Also worked for me

same issue when upgrading from v0.25.0 to v0.26.1