-
Notifications
You must be signed in to change notification settings - Fork 125
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
Cannot run with viewer role #9
Comments
Hi @tjun! I believe this could be solved by just updating your role to have list permissions on |
I think we’re talking about GKE Viewer role here. Have you tried “viewer” role in Kubernetes rbac? I suspect GKE Viewer doesn’t let the subject to view Secrets in a cluster, for a good reason. |
Thanks!
Yes, I already have a viewer role in Kubernetes rbac for the target namespace. Doesn't have cluster level viewer role. |
Kubectl tree tries to retrieve every single API resource in your cluster. In the future we might introduce an --ignore-inaccessible option (and log those failures as warnings), but for now we flat out fail. |
In querying APIs, failed to list
secret
and cannot show the result.When I try to run kubectl tree with viewer role, got the following error:
The text was updated successfully, but these errors were encountered: