ArtifactGC not executing on archiveLogs
when specified in Workflow level
#13421
Labels
area/archive-logs
Archive Logs feature
area/artifacts
S3/GCP/OSS/Git/HDFS etc
area/gc
Garbage collection, such as TTLs, retentionPolicy, delays, and more
P3
Low priority
solution/workaround
There's a workaround, might not be great, but exists
type/bug
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?
The artifactGC pod was not being deployed after workflow deletion. We have tested it with CronWorkflows also.
We deploy argo-workflows with helm.
In our use case we use
archiveLogs: true
and AWS IRSA to authenticate from the service accounts (workflow and argo server). At workflow default configuration we use the following:With the workflow below, both the generated logs and the files saved as artifacts are correctly removed from the s3 bucket.
But when we comment out the lines containing info about artifacts in the different workflow templates, the logs are not removed from the bucket.
After this configuration change, we receive this message in workflow status:
We have found a workaround, adding this metadata for both Workflows and CronWorkflows:
After adding it, the logs are deleted from s3 bucket, but it's necessary to fix it.
Version(s)
v3.5.8
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
The text was updated successfully, but these errors were encountered: