-
Notifications
You must be signed in to change notification settings - Fork 42.8k
Role/ClusterRole creation doesn't cross authorizers nicely #43409
Copy link
Copy link
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.
Milestone
Description
In order to create an RBAC role, I need to have all of the permissions that exist in the role, through RBAC. It doesn't matter If I have all the permissions through another authorizer.
On GKE, for example, if I want to use my Google identity to create a role, I first have to create an RBAC RoleBinding giving myself the cluster-admin role, even if I am the owner of the project that has the GKE cluster.
We should authorize role creation in a way that allows "super users" from other authorizers to use RBAC.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.sig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.