timed out waiting to elevate kube-system RBAC privileges: Post: Service Unavailable

[kikobg]

Hello,

I am trying to start local cluster on Windows 10 using minikube( v0.28.2 ). Everything runs fine until the step
Starting cluster components...
where I stumbled on the following issue:

E0727 15:00:05.218387 15960 start.go:300] Error starting cluster: timed out waiting to elevate kube-system RBAC privileges: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings: Service Unavailable

Do you know what might be the reason?

Best regards

[amsaha]

I am seeing the same issue on macOS High Sierra 10.13.6 (17G65).

[Karmatronics]

Same thing for me also on macOS High Sierra 10.13.6 :(

[bakunin95]

Same issue on macOS High Sierra 10.13.6

[dprasanthv]

Uninstall/delete all minikube related files
1.1. minikube delete
1.2. rm /usr/local/minikube
1.3. rm -rf ~/.minikube

reinstall minikube.

[tbachman]

Tried the above (although for 1.2, a minor change is needed -- it's in /usr/local/bin), and still failed. macOS High Sierra 10.13.4.

[kikobg]

Works ok on Ubuntu VM(16.04) though. I managed to start a cluster on the VM with enabled nested virtualization and VirtualBox 5.2 installed.

[tbachman]

Not sure if this will help others, but this problem went away after upgrading VirtualBox.

[dinigo]

Same here. Can you tell the latest stable/working version?

Removing config and uninstalling didn't make the trick

[tbachman]

FWIW, I upgraded to 5.2.16 r123759 (Qt5.6.3) on macOS. I can't remember what version I was running previously, but it was at least a year old, maybe as much as two.

[nilebox]

Updating Virtual Box to the latest version helped on macOS as well.

[tbachman]

Just to provide a bit more background -- I realized that my localhost couldn't communicate with the VM on the host-only network (vboxnet4 in my case), which I believe is why I was getting this error from minikube. I did some googling that led me to links describing problems with older versions of Virtual Box, which is why I tried the upgrade.

[bakunin95]

I updated VirtualBox from 5.2.12 to 5.2.16 and i still get the error, i also tried other drivers.
The only thing that works for me right now is:
minikube start --bootstrapper=localkube

but localkube is deprecated so i don't really like the solution.

[tbachman]

Just as an FYI, I also followed the steps from dprasanthv to delete the VM after upgrading (wanted to make sure there wasn't any issue with the VM itself). I doubt this will make a difference, but I thought I should mention it, as it's something else that I did.

[zieg8301]

I'm experiencing the same issues above, but on Sierra (10.12.6). Updated virtualbox to latest version, cleaned and reinstalled minikube. Only thing that works is using localkube as the bootstrapper.

[InTheCloudDan]

Also hitting this, none of the above suggestions are working for me. Localkube seems to start but kubectl commands hang still.