-
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
Exceeded Quota Causes Failed Workflows #3645
Comments
Please change - resubmitPendingPods: True
+ resubmitPendingPods: true Boolean values are case sensitive |
Feel free to repoen if this doesn't fix your issue |
This didn't fix my issue |
@simster7 I can't seem to reopen this myself |
Will take another look |
It may already be fixed by #3490 I haven't been able to test the prerelease |
Please test in |
Does this version need to be present on the cluster or is it enough to just have the pre-release CLI? |
It needs to be present on the cluster |
I don't have the permission to do this |
I'll take a look |
Hi @KPostOffice, sorry for the delay. I tested this in |
Will close this again unless you confirm that you've tested this in |
I still seem to be having issues. Does the executor that I'm using make any difference? |
I've created a new image for testing if you would like to try it: argoproj/workflow-controller:fix-3791 . |
👍 |
I've created another test image: argoproj/workflow-controller:fix-3791. Can you please try it out to confirm it fixes your problem? |
Checklist:
What happened:
Workflow failed due to exceeding CPU quota and also due to exceeding memory quota
What you expected to happen:
Pod should stay in pending state until it is able to get the necessary resources.
How to reproduce it (as minimally and precisely as possible):
*replace cpu limit and request with memory to test memory
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
Related
#3419
#3490
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: