-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
3.5 Server OOM when too many executions of CronWorkflows #12645
Comments
You mean the history view in the For pagination for the
The |
Thanks for confirming.
How can this be accomplished?
The perception was wrong. |
We'd just need to add a argo-workflows/ui/src/app/cron-workflows/components/cron-workflow-details/cron-workflow-details.tsx Line 74 in 33c51ed
Would you like to work on that?
In 3.5.x I believe they should be included by default since it has the unified API/UI. |
Thank you, I would love to work on it, can you assign me to it? |
You don't need to be assigned to work on something, can just submit a PR. |
Pre-requisites
:latest
What happened/what did you expect to happen?
This occurs when trying to view the details of each cron-workflows or workflow-template UI, which has a lot of history.
There was nothing like that in the argo-server logs.
Version
v3.5.4
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.
Any workflow is acceptable.
Logs from the workflow controller
workflow-controller does not seem to be involved.
Logs from in your workflow's wait container
workflow-controller does not seem to be involved.
The text was updated successfully, but these errors were encountered: