FYI this bug is visible in two cases so far
On our deployment of pipelines as well, logs get wiped away once in few weeks- what will be needed is configuration to persist the logs to a persistent storage, as well as support for archival
SG. This is open for contributions if you are interested. An object store would be great to persist the logs. If the implementation uses Minio Client, we would be able to persist the logs on GCS/S3/GCP.
Description of the solution:
Short term workaround from @amygdala
To clean up PODs:
As @animeshsingh suggested in https://github.com/kubeflow/pipelines/issues/940, we could use the latest Argo executor to save logs to S3/GCS persistent volume when the archiving flag is enabled.
What is the status on this issue? Has there been any updates or contributions? Or is there any documentation on how to enable Argo archiving as suggested above?
GC is implemented now. You can set the TTL as persistence agent env here https://github.com/kubeflow/pipelines/pull/1802/files#diff-f4326ec4a2f4f6b219c2aab8887f6c85R21
The log can be persisted with ARGO_ARCHIVE_LOGS
https://github.com/kubeflow/pipelines/pull/2081
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Both are supported