-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recipe 10.2 'Listing and viewing Access Control Information' #9
Comments
Meanwhile. using Minikube 0.29.0 with '--extra-config=apiserver.Authorization.Mode=RBAC' would hang 'minikube start'. But later I used '--extra-config=apiserver.Authorization-Mode=RBAC' instead, the hang disappeared. |
You have a copy past mistake in there (I checked, it's correct in the book): it should be |
Hi Michael
I sill gor error via using --as=system:serviceaccount:sec:myappsa
no - RBAC: role.rbac.authorization.k8s.io "sec:podreader" not found
Can I reopen this issue?
Michael Hausenblas <notifications@github.com> 於 2018年10月16日 週二 下午3:40寫道:
… You have a copy past mistake in there (I checked, it's correct in the
book): it should be --as=system:serviceaccount:sec:myappsa and not
--as=system-serviceaccount:sec:myappsa
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AlDjxq7Sgai9zzayKVUj9yOvev4ZEaTuks5ulY16gaJpZM4Xdnnm>
.
|
Well, that's strange, isn't it? :) What does |
So @bennybhlin not sure about this one. I can't reproduce it as it stands. What exactly was your setup? What steps did you do? |
Did you create the rolebinding as well ? BTW: you can just paste the text output using triple quotes like this:
instead of pasting pictures... |
I used the 'pod-with-sa.yaml' example here to create serviceaccount sec/myappsa; however, if I just enter the command of sec. 10.2 'kubectl -n sec auth can-i list pods --as=system-serviceaccount:sec:myappsa', I would get an error message below (no RBAC policy matched):
Even I'd follower recipe 10.3 to create required role and role binding under namespace 'sec', I still could not verify whether serviceaccount sec/myappsa is capable of get/list pods in namespace 'sec'.
What did I miss?
The text was updated successfully, but these errors were encountered: