-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support archived workflows logs in UI from archived logs #7830
Comments
Hi @alexec , would you mind providing more details on this. |
If I understand correctly - the current UI does not make the request to get the logs (output artifacts) by the workflow's UID? because the server's endpoint for it exist. |
Does this relate to the Log UI "All" option not showing nothing after pods are garbage collected? Or, should that be considered a separate issue? On a side note, what does this recommendation in the docs mean?:
Are there some known issues? Also, does kubernetes provide any facility for collecting and returning logs for garbage collected pods, and then can argo workflows use this facility? I ask because viewing logs in the argo workflows UI is very convenient, and one of the main "selling points" of the application in my mind |
Not quite. That is a Kubernetes limitation, not an Argo issue. k8s no longer has logs after the Pods are GC'd.
A pretty conventional cluster set-up is to have EDIT: The archive logs docs are getting more specific improvements around recommendations in #12597 |
Not sure if #11121 ended up fixing this as well. cc @terrytangyuan |
It's supported. Re-open if not. |
Summary
Currently, if you open an archived workflow, you are not able to see logs in the log viewer, even if the logs were archived to 'main.log'. We could fix this.
Use Cases
When would you use this?
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: