Minikube: --extra-config=apiserver.authorization-mode=RBAC causes minikube start to hang: unknown flag: --Authorization.Mode

Created on 8 May 2018 · 10Comments · Source: kubernetes/minikube

The documentation at:

https://github.com/kubernetes/minikube/blob/master/docs/configuring_kubernetes.md#examples

Says:

To set the AuthorizationMode on the apiserver to RBAC, you can use: --extra-config=apiserver.authorization-mode=RBAC.

But this causes Minikube to hang.

minikube start -v 10 --extra-config=apiserver.Authorization.Mode=RBAC
...
Setting up kubeconfig...
Starting cluster components...
^C

The API server no longer accepts that command line argument:

$ minikube ssh
$ docker logs 9f3405f5237a
Error: unknown flag: --Authorization.Mode
Usage:
  kube-apiserver [flags]

...

$ minikube version
minikube version: v0.26.1

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

causapiserver-flags kinbug triagobsolete

Source

wallrj

👍2

Most helpful comment

In fact the flag --extra-config=apiserver.Authorization.Mode=RBAC is no longuer valide after version v25.2.
You must use --extra-config=apiserver.authorization-mode=RBAC instead of --extra-config=apiserver.Authorization.Mode=RBAC.

IMHO it would have been preferable to deprecated the old flag before to make it unusable.

jpiccaluga on 11 Sep 2018

👍8 🎉1

All 10 comments

I ran into this same issue after upgrading to v0.26.1.

This workaround fixed it for me: --extra-config=apiserver.authorization-mode=RBAC.

debtcollapse on 8 May 2018

👎5 👍4 🎉2

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 6 Aug 2018

/remove-lifecycle stale

jpiccaluga on 28 Aug 2018

This issue is still present in last release v28.2 . IS it possible to fix it?
Last working version was v25.2

jpiccaluga on 28 Aug 2018

mukgupta on 9 Sep 2018

IMHO it would have been preferable to deprecated the old flag before to make it unusable.

jpiccaluga on 11 Sep 2018

👍8 🎉1

Yes, with v0.28.2 it will fail with the wrong key for the RBAC setting.

"E0912 14:25:08.682389 43508 start.go:300] Error starting cluster: kubeadm init error"

Value key must be lowercase with a dash, very important!

A subtle difference for those who are going too fast and do not notice this slight syntactic change. Older sites and blogs still have the old setting and can easily be copied to a recent version of Minikube and cause confusion.

javajon on 12 Sep 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 18 Dec 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 17 Jan 2019

Obsolete: documentation was updated, RBAC is default.