-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 "argo delete --force" to force deletion of a workflow which has a finalizer #9315
Comments
@sarabala1979 Added this per your suggestion. Can you add it to "Artifacts" project? |
Would it make sense to add this |
You can add an enhancement Issue for that if you like. The UI would of course still need to offer the "non-force" option as well.
Hmm, there might be a bug if that's happening. The way it should work is that if you set your artifact GC to "OnWorkflowCompletion" for example, then when the Workflow completes, only artifacts that actually exist should get deleted, and then once all of these artifacts have been deleted the finalizer gets removed. If you believe there's a bug, you can write up an issue and let me know. I'm curious whether an Artifact GC Pod was created and if there's an associated WorkflowArtifactGCTask ( |
Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com> Signed-off-by: juchao <juchao@coscene.io>
Artifact GC creates a finalizer to prevent Workflows from being deleted until their artifacts have been deleted. But if the artifacts fail to get deleted, the finalizer will remain.
This CLI command would force delete a workflow which has a finalizer, removing the finalizer first. (And thus the ArtifactGCTask, which is owned by it, and the ArtifactGC pod owned by the ArtifactGCTask would all get deleted.)
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: