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
I'd like to be able to set the default deletion propagation policy for all apps. Even better would be to set the default on a project or application level directly.
Motivation
Some services we deploy are critical enough that we would like to default deletion propagation policy to "non-cascading". When removing those services, we'd rather remove them from ArgoCD first, then perform cleanup via kubectl.
I could also see this being used by others to default to "background" if needed for a particular service.
There is also an ask to change the default behavior without a setting, but I think allowing a setting would be more flexible: #5724
Proposal
For a global setting, I think it could be a new key application.defaultDeletePolicy in the argocd-cm ConfigMap.
For project or application level, it could also be a new key defaultDeletePolicy in the individual spec.
The text was updated successfully, but these errors were encountered:
Summary
I'd like to be able to set the default deletion propagation policy for all apps. Even better would be to set the default on a project or application level directly.
Motivation
Some services we deploy are critical enough that we would like to default deletion propagation policy to "non-cascading". When removing those services, we'd rather remove them from ArgoCD first, then perform cleanup via kubectl.
I could also see this being used by others to default to "background" if needed for a particular service.
There is also an ask to change the default behavior without a setting, but I think allowing a setting would be more flexible: #5724
Proposal
For a global setting, I think it could be a new key
application.defaultDeletePolicy
in theargocd-cm
ConfigMap.For project or application level, it could also be a new key
defaultDeletePolicy
in the individual spec.The text was updated successfully, but these errors were encountered: