[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
I have workflows, which don't use artifacts, but in case of errors, I'd like to have access to the logs (obviously). Also, to be more resources efficient I usually use podGC to delete the pod as soon an possible and I also enabled log archiving, so that I have so logs persisted. So far so good.
The problem is, that once the workflow is automatically deleted (because of the ttl setting), the logs remain in the artifact repository ... forever. Since the log files are technically artifacts (are they not?), because the workflow controller puts them in the artifact repository, I would expect that the artifactGC will clean them up as well, even if there are no other artifacts being used in that workflow. I'd like to add that once I have at least 1 artifact in the workflow, everything (artifacts AND logs) are being cleaned up as expected.
TLDR: workflow without using artifacts + artifactGC enabled + podGC enabled + archiveLogs enabled = lots of orphaned logs in the artifact repository
Version(s)
v3.5.11
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
I have workflows, which don't use artifacts, but in case of errors, I'd like to have access to the logs (obviously). Also, to be more resources efficient I usually use podGC to delete the pod as soon an possible and I also enabled log archiving, so that I have so logs persisted. So far so good.
The problem is, that once the workflow is automatically deleted (because of the ttl setting), the logs remain in the artifact repository ... forever. Since the log files are technically artifacts (are they not?), because the workflow controller puts them in the artifact repository, I would expect that the artifactGC will clean them up as well, even if there are no other artifacts being used in that workflow. I'd like to add that once I have at least 1 artifact in the workflow, everything (artifacts AND logs) are being cleaned up as expected.
TLDR: workflow without using artifacts + artifactGC enabled + podGC enabled + archiveLogs enabled = lots of orphaned logs in the artifact repository
Version(s)
v3.5.11
Paste a minimal 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 workflow controller
Logs from in your workflow's wait container