Skip to content
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

Add support for the escalate RBAC verb #83

Open
raesene opened this issue Mar 24, 2021 · 0 comments
Open

Add support for the escalate RBAC verb #83

raesene opened this issue Mar 24, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@raesene
Copy link

raesene commented Mar 24, 2021

What would you like to be added

At the moment the escalate verb which is available on Kubernetes cluster roles does not appear to be supported

kubectl-who-can escalate clusterroles
Error: resolving resource: the "clusterroles" resource does not support the "escalate" verb, only [create delete deletecollection get list patch update watch]

It would be good if escalate was factored into the tool. There's probably two ways that it might make sense to include this. the first would be the ability for the command above to return principals which have access to escalate. The second way (which would be trickier to implement) would be to show principals which have access to escalate on clusterroles as having all other rights.

Why is this needed

The escalate right essentially allows for principals which have access to it to gain cluster admin rights at any time they want. As mentioned in the documentation having access to escalate allows a principal to edit a cluster role (or role) to grant permissions the user did not previously have.

In a standard kubeadm cluster, there is a service account which has this right, the clusterrole-aggregation-controller. There's a blog here that shows how someone with that account's service account token can escalate to cluster-admin.

@raesene raesene added the enhancement New feature or request label Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant