-
Notifications
You must be signed in to change notification settings - Fork 31
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
Support container creation when resource quotas are hit #87
Comments
In earlier versions kubedock was using deployments, and had the option to use jobs. Deployments were problematic when the orchestrated containers were actually one-off jobs (jobs did solve that). A retry option might make sense and probably leads to increased succes when orchestrating, but tests might still fail because of time-outs in the actual tests as well. Something that might work already, is setting lower requests and limits (via labels, global settings, or a global pod template). |
Yes, lowering requests and limits relieves the problem temporarily, and it's definitely something we're doing now to work around the problem, but it does not solve the problem permanently - even on lower limits the pod might hit the quota and get denied. |
Currently, when kubedock creates pods and you hit a resource quota, the request fails with this error:
Context: we run kubedock as a sidecontainer on Tekton to support java testcontainers.
Is it possible to support creating pods in this situation without having the request fail immediately?
Some solutions I considered:
Deployment
instead of aPod
to schedule the containerAnd maybe there are other options?
The text was updated successfully, but these errors were encountered: