search

argoproj / argo-workflows

Workflow Engine for Kubernetes
https://argo-workflows.readthedocs.io/
Apache License 2.0
15.11k stars 3.21k forks source link

UI init/wait logs overwritten with "no artifact logs are available" after pod deleted #13894

Open tooptoop4 opened 1 week ago

tooptoop4 commented 1 week ago

you run any workflow, click on the logs button in the ui, select init container, it shows those logs, but then once pod dies the logs are no longer visible and "no artifact logs are available" error appears. i think the react ui could be made to not overwrite the log display if you already had it open (i understand anyone clicking the links for the first time after pod died, should still see the error)

pseudocode: before fetching next set of logs, preserve current logs in memory if next set of logs is unavailable then display what is in memory

shuangkun commented 6 days ago

Is it too resource-intensive to store it in memory? Can we fetch the log of init/wait from the server and display it in the UI? We currently achieve this by taking logs from cloud provider log systems, such as Alibaba Cloud SLS, when a pod has been deleted, and displaying them on the UI.