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
Is your feature request related to a problem? Please describe.
Currently we are using Kor to produce a report of unused resources across our K8s infra. Our users need to escalate to an admin user via user impersonation to run high risk activities such as a PVC delete. Currently if we try to use the delete commands it does not work because Kor does not accept a --as admin flag
Describe the solution you'd like
Allow for a --as flag for running deletions from the Kor CLI
Describe alternatives you've considered
Currently I have got around this by running Kor and outputting the resources to be cleaned to json then iterating over a list of resources and the kubectl command to delete the resource. It would be great if we could remove this step and allow for user impersonation.
The text was updated successfully, but these errors were encountered:
Hi @logan-bobo this is definitely a good feature.
I'm not super familiar with user impersonation so I'm not sure what the cost of adding and maintaining this would be. So I can't guarantee it will be added.
You're welcome to work on this and we can see what this requires, my feeling is this won't be too hard
Is your feature request related to a problem? Please describe.
Currently we are using Kor to produce a report of unused resources across our K8s infra. Our users need to escalate to an admin user via user impersonation to run high risk activities such as a PVC delete. Currently if we try to use the delete commands it does not work because Kor does not accept a
--as admin
flagDescribe the solution you'd like
Allow for a
--as
flag for running deletions from the Kor CLIDescribe alternatives you've considered
Currently I have got around this by running Kor and outputting the resources to be cleaned to json then iterating over a list of resources and the kubectl command to delete the resource. It would be great if we could remove this step and allow for user impersonation.
The text was updated successfully, but these errors were encountered: