minikube fails when using rbac and kubeadm as bootstrapper

[MansM]

minikube start --kubernetes-version v1.8.0 --bootstrapper kubeadm --extra-config=apiserver.Authorization.Mode=RBAC
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components..

after like half an hour still waiting

minikube version: v0.22.3
macOS Sierra
virtualbox: 5.1.28-117968

cat ~/.minikube/config/config.json
{
"WantReportError": true,
"cpus": 4,
"dashboard": true,
"ingress": true,
"memory": 6144,
"registry": false
}

[r2d4]

RBAC is enabled in the kubeadm bootstrapper by default, so you should be able to do a

minikube delete
minikube start --bootstrapper kubeadm --kubernetes-version v1.8.0

If you start with --v 10 and --logtostderr you might see why it fails, although it shouldn't hang.

Once I write documentation for #2034 it should be more clear that the kubeadm bootstrapper takes a different form for the --extra-config flag.

[MansM]

also noticed that helm charts with pvc's fail as no volume gets created

[r2d4]

There is no dynamic provisioning in the kubeadm bootstrapper yet

[r2d4]

Fixed with #2037