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
dgrove-oss
changed the title
Configurable automatic cleanup after AppWrapper completion
Configurable automatic cleanup for Successful AppWrappers
Apr 1, 2024
For AppWrappers that end in the Succeeded state we follow MCAD and do not delete the resources until the AppWrapper itself is deleted. It would be fairly easy to add automatic deletion in the Succeeded state (after a fairly long time period, as a Succeeded AppWrapper has no pods and therefore is not consuming significant resources).
dgrove-oss
added a commit
to dgrove-oss/appwrapper
that referenced
this issue
Apr 30, 2024
Consider adding configurable automatic cleanup after completion of an AppWrapper.
Can draw inspiration from similar feature on Jobs (https://kubernetes.io/docs/concepts/workloads/controllers/job/#ttl-mechanism-for-finished-jobs).
We may want to have different default behavior for successful vs. failed jobs.
The text was updated successfully, but these errors were encountered: