Name of Feature or Improvement
Delete successfully completed AppWrappers after successTLLDuration
Description of Problem the Feature Should Solve
Currently when successTLLDuration expires a successfully completed AppWrapper
deletes the wrapped resources, but the AppWrapper itself is not deleted.
Users have requested a complete cleanup (similar to Job) where after successTLLDurartion
expires, the AppWrapper is also automatically deleted by the system.
Describe the Solution You Would Like to See
I would propose implementing this guarded by an operator-level configuration. It would default to
enabled, but could be disabled via the configuration for a cluster by a batch-admin. An alternative would
be to support per-AppWrapper annotations to allow opt-out (or opt-in), but there isn't a strong demand
for keeping successfully completed AppWrappers around indefinitely on clusters where the normal
case is to clean them up
Name of Feature or Improvement
Delete successfully completed AppWrappers after successTLLDuration
Description of Problem the Feature Should Solve
Currently when successTLLDuration expires a successfully completed AppWrapper
deletes the wrapped resources, but the AppWrapper itself is not deleted.
Users have requested a complete cleanup (similar to Job) where after successTLLDurartion
expires, the AppWrapper is also automatically deleted by the system.
Describe the Solution You Would Like to See
I would propose implementing this guarded by an operator-level configuration. It would default to
enabled, but could be disabled via the configuration for a cluster by a batch-admin. An alternative would
be to support per-AppWrapper annotations to allow opt-out (or opt-in), but there isn't a strong demand
for keeping successfully completed AppWrappers around indefinitely on clusters where the normal
case is to clean them up