-
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
Logging does not work after pod completes #1005
Comments
Yes, the log is gone when pod is gone. It is the default behavior of kubernetes. See more infomation from https://kubernetes.io/docs/concepts/cluster-administration/logging/ |
@aisensiy I wonder why argo chose to remove the pods after they are done. Another option is to follow the pattern of Kubernetes jobs: It will keep the pods unless deleted by users. |
Workflow controller (v2.2.0) has ability to save logs in artifacts repository: UI don't use that feature yet, though. This will be resolved in #1018 |
I guess we can close it. @strin please feel free to reopen if necessary |
This archiveLogs setting isn't working for me. I don't see anything in any logs for controllers, sensors, events in the namespace that would indicate why this is not working. |
Is this a BUG REPORT or FEATURE REQUEST?:
Bug report.
What happened:
We are running argo on Google Kubernetes Engine, with autoscaling enabled. Argo launched the container successfully, but after it completes the node gets deleted by autoscaler and the completed pod is no longer available.
What you expected to happen:
In Argo UI clicking on logs should reveal the container logs
How to reproduce it (as minimally and precisely as possible):
Launch a job on GKE with the following config enabled.
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: