You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A cool feature would be to define a potential grantee in an escalation grant directly, for example in the K8sRoleBinding grant we could write something like this
In that case, kudo will create the role binding not for the requestor, but for the grantee defined by the policy in the namespace picked by the policy.
This could open up a bunch of cool use cases like granting temporarily more permissions to a workload.
What needs to be done?
A cool feature would be to define a potential grantee in an escalation grant directly, for example in the
K8sRoleBinding
grant we could write something like thisIn that case, kudo will create the role binding not for the requestor, but for the grantee defined by the policy in the namespace picked by the policy.
This could open up a bunch of cool use cases like granting temporarily more permissions to a workload.
Kudos to @dduportal for the idead 🎉
Acceptance Criteria
The text was updated successfully, but these errors were encountered: