-
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
OOMKilled error for gitclone does not say which container was killed? init, main, wait ? #10007
Open
2 of 3 tasks
Labels
Comments
my guess is argo-workflows/workflow/controller/operator.go Lines 1581 to 1657 in 54621cc
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
i have 5g memory set for this step, sometimes works, sometimes doesn't
not sure if i need to increase init or wait container memory too?
is it possible to make the error message say which container was OOMkilled?
Version
3.4.3
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.
https://github.com/argoproj/argo-workflows/blob/9f5759b5bd2a01d0f2930faa20ad5a769395eb99/examples/input-artifact-git.yaml like this one
Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
The text was updated successfully, but these errors were encountered: