-
Notifications
You must be signed in to change notification settings - Fork 140
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
Add limits for simultaneous test executions #3584
Comments
I would prefer to queue tests if there are not available resources to execute them. |
sure - either could be possible/configurable - let the user decide |
I would like to see this feature as well (or a queue as Bruno suggests), it is important for me to limit the number of test pods running concurrently to avoid resource exhaustion. |
Perhaps something can be done with resource quotas: https://kubernetes.io/docs/concepts/policy/resource-quotas/ Not sure if it is possible to communicate the quota error through the testkube dashboard. |
Action plan:
|
@TheBrunoLopes, would we really like to have it only globally? Even we are encountering problems now because of the lack of the concurrency configuration on the test & test suite level. |
yeah, we can also have it at the Test / Suite level. |
@exu @rangoo94 @jmorante-ks to review architectural changes. |
duplicated #5463 |
To help me ensure that I'm not overloading my cluster I would like to be able to configure
When any of those limits are met - the Run button in the UI should be disabled with a corresponding warning message - "simultaneous test execution limit of XX reached" (or something like that)
The text was updated successfully, but these errors were encountered: