-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Unable to delete pod from ArgoCD UI using the action #12777
Comments
The Resource-level The current plan is to enable this through either impersonation support or improved actions support. For now, the only way to enable something like pod restart is to enable the |
Any idea when new features are scheduled to release? |
How soon can this kind of functionality be included in the release ? |
Well, I hope to merge an open PR for 2.8 which will allow creating a resource via a custom action. Once that's merged, it will be trivial to enable deleting resources via actions. Honestly I feel like adding a new |
@crenshaw-dev which is this PR you are referring to? |
Version 2.8 is very cool!!! Now you can do it? |
@bygui86 this is the PR: #12925 @SergeyLadutko the above PR enabled actions to update resources. The next step would be a PR that enables actions to delete resources. |
@crenshaw-dev does the update include also the create? |
Oh, apologies, I meant to say "create". Actions could always update resources. :-)
They currently allow managing resources that the application would be allowed to manage anyway. So, AppProject rules are of course enforced. |
Hey guys, can you tell me if there's some kind of update? |
💯 It would be very useful to have this delete functionality via ArgoCD |
Checklist:
argocd version
.Describe the bug
When using the RBAC configuration to allow some permissions to default
role:readonly
.Delete the Pods permissions are not working as expected.
Following rule is used as per the documentation shared here
Rule:
p, role:readonly, applications, action/core/Pod/delete, prod/*, allow
The issue is Pod object in kubernetes has empty which I believe is not parsed correctly and ArgoCD always returns permission denied error when someone assuming this role tries to perform delete action on Pods, however it works for Deployment/DaemonSet & even Rollout objects.
p, role:readonly, applications, action/apps/Deployment/delete, prod/*, allow
p, role:readonly, applications, action/apps/argoproj.io/delete, prod/*, allow
To Reproduce
Assign above rule and try to delete the Pod from ArgoCD UI.
Expected behavior
Should be able to delete the Pod from ArgoCD UI.
Screenshots
Version
Logs
When trying to delete pod using above RBAC. Some of the sensitive information is masked.
The text was updated successfully, but these errors were encountered: