[frontend] Pipeline logs persistence

[rohitgujral]

I'm trying to persist the pipeline pod logs so that if pod gets deleted then logs should be available for the pipeline runs.
I added archiveLogs: true to the argo/base config-map and restarted pipelines deployment but still after deleting the pod, im not seeing logs.

Is there any other step which needs to be done ?
kubeflow version - 1.0.2 and argo version - 2.3.0

[zijianjoy]

Possible related issue: #6428

One thing we can do is to capture the main.log from output Artifact, and visualize it in Logs tab. Welcome contribution for making this change for KFPv1.

[stale]

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.

[AndersBennedsgaard]

This should probably be closed in favor of #6428

[thesuperzapper]

@AndersBennedsgaard I don't think #6428 is related to this issue.

The issue raised here was that in KFP v1, the "logs" tab did not fall back to the main.log artifact (even though we were exposing it in the other UI tab).

However, the same issue is present in the KFP v2 UI (and it's actually worse), because we dont even capture the main.log as an output artifact. Let's continue the discussion about fixing it in KFP V2 on:

• [feature] display main.log as artifact for each step #10036

/close

[google-oss-prow]

@thesuperzapper: Closing this issue.

In response to this:

@AndersBennedsgaard I don't think #6428 is related to this issue.

The issue raised here was that in KFP v1, the "logs" tab did not fall back to the main.log artifact (even though we were exposing it in the other UI tab).

However, the same issue is present in the KFP v2 UI (and it's actually worse), because we dont even capture the main.log as an output artifact. Let's continue the discussion about fixing it in KFP V2 on:

• [feature] display main.log as artifact for each step #10036

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.