That would prevent a resource from being deleted when we delete an Application. Currently, there is no way to leave orphaned resources without removing the finalizer from the Application
ArgoCD Version 1.7.11
Motivation
We deploy ArgoCD on Openshift to manage all our cluster configuration. There are some resources that we have to configure, but these resources can never be deleted from a cluster. However, in some use cases we want to reconfigure these resources with a different Application, however we cannot delete the old application as ArgoCD gets stuck in an infinite loop of trying to delete the old Application.
Proposal
Either update the deletion login to skip resources with the annotation:
Summary
Proposal is to introduce an annotation like:
That would prevent a resource from being deleted when we delete an Application. Currently, there is no way to leave orphaned resources without removing the finalizer from the Application
ArgoCD Version 1.7.11
Motivation
We deploy ArgoCD on Openshift to manage all our cluster configuration. There are some resources that we have to configure, but these resources can never be deleted from a cluster. However, in some use cases we want to reconfigure these resources with a different Application, however we cannot delete the old application as ArgoCD gets stuck in an infinite loop of trying to delete the old Application.
Proposal
Either update the deletion login to skip resources with the annotation:
Or simply introduce a new annotation: