-
Notifications
You must be signed in to change notification settings - Fork 9
Istio RBAC install failed on RBAC cluster #4
Comments
Had to use admin user w/ client cert to fetch the credential, then the errors went a way :/
|
Yes, I think this is working as intended, granting permissions requires admin user. We may need to document it better ( or k8s RBAC docs should make it more obvious ). |
@saturnism I encountered the same problem but I don't understand
It is a not command. What are you talking about? |
This is a gcloud command if you use GKE (Google Container Engine). There have been many changes in RBAC since then, and it was fixed in the master. I suggest to take the latest istio-rbac-beta.yaml file from the master branch. |
@andraxylia I am sure that
Is NOT a valid gcloud command even you set
in a .bashprofile. the syntax is
It was not clear. |
Perhaps you might as well set
|
This needs to be re-opened. It seems like we may have lost it from the doc. Need to add admin user explicitly to the role binding:
|
Looks like this crept back with our 0.2 docs, we need to go restore this bit of info. |
This is fixed in istio/istio.io#569 |
Running Kubernetes 1.6.2 on GKE
it looks like rbac is supported:
error when applying
istio-rbac-beta.yaml
The text was updated successfully, but these errors were encountered: