project-codeflare / project-codeflare/appwrapper

Automatic deletion of successfully completed AppWrappers after successTTLDuration

Open
#353 0 comments 0 reactions 1 assignee View on GitHub

@dgrove-oss is already working on this.

Since Apr 30, 2025.

enhancement
Dominant language
Go
Stars
19
Forks
15
Avg merge
1d 12h
Merged PRs (30d)
7

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.