-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
artifactGC does not run when the output artifact uses archive: none
#12857
Labels
area/artifacts
S3/GCP/OSS/Git/HDFS etc
area/gc
Garbage collection, such as TTLs, retentionPolicy, delays, and more
P3
Low priority
type/bug
Comments
My guess is that an But I'm not a go developer, definetly not familiar with argo source, and this could probably cause some side effects - eg. this deletes the whole dir, so if other, non workflow related stuff was in there, it would delete that as well. |
agilgur5
added
area/gc
Garbage collection, such as TTLs, retentionPolicy, delays, and more
P3
Low priority
labels
Mar 28, 2024
agilgur5
changed the title
artifactGC does not run when the output artifact is not archived
artifactGC does not run when the output artifact uses Mar 29, 2024
archive: none
agilgur5
pushed a commit
that referenced
this issue
Jul 6, 2024
Signed-off-by: Tianchu Zhao <[email protected]> Signed-off-by: Anton Gilgur <[email protected]> Co-authored-by: Anton Gilgur <[email protected]> (cherry picked from commit a929c8f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/artifacts
S3/GCP/OSS/Git/HDFS etc
area/gc
Garbage collection, such as TTLs, retentionPolicy, delays, and more
P3
Low priority
type/bug
Pre-requisites
:latest
What happened/what did you expect to happen?
If I use an output artifact with
archive: none: {}
andartifactGC
, then the artifacts are not deleted with the error:Version
v3.5.4
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the garbage collection pod
Logs from in your workflow's wait container
no relevant wait container. the artifact is uploaded successfully to
The text was updated successfully, but these errors were encountered: