-
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
Resource template logs for spark application don't get archived in artifact repo #9900
Comments
Your resource needs some metadata, take a look at the example: https://github.com/argoproj/argo-workflows/blob/master/examples/k8s-resource-log-selector.yaml |
@ajkaanbal This is for pulling the logs from the pods created by the spark CRD (spark-driver, spark-executor) |
@Freia3 Current Resource template will not support archiving the log. Do you like to work on this enhancement? |
@sarabala1979 Ok, thanks for the information, couldn't find this in the docs. No, I can't work on this enhancement. |
@sarabala1979 Hello I wish to contribute on this one, It is relevant for my team and I believe that the fix is straightforward. From what Ive seen there are to ways to solve it,
tbh I think 2 is a better option, wdyt? |
I'm probably in agreement about 2 being the right way to do it. @sarabala1979, can you pitch in? |
Hey @sarabala1979 do you want me to create pull request? |
Hi We would be interested in this functionality too. I wonder whether there are any updates on it? Also, to clarify, we would in interested in getting the logs for containers other than |
Signed-off-by: shuangkun <[email protected]>
Pre-requisites
:latest
What happened/what you expected to happen?
I have an Argo Workflow running a Spark application (using the spark-operator). I want to archive the logs of this workflow in an artifact repository, but this does not work.
When running the hello-world workflow, the logs do get archived.
yaml files to reproduce: https://github.com/Freia3/argo-spark-example
Version
v3.4.2
Paste a small 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
No resources found in argo namespace.
The text was updated successfully, but these errors were encountered: