-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: chrome-node-scaledjobs.yaml don't apply ttlSecondsAfterFinished and minReplicaCount #1906
Comments
@cr-liorholtzman, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@msvticket do you know? |
@diemol Just a small correction, I think it should be under jobTargetRef section according this exmaple - kedacore/keda#630 |
Another available solution which does seem to work is to use these two on the scaledJobOptions section:
|
It is not a bug that jobs stay around for a while. There are default values for successfulJobsHistoryLimit and failedJobsHistoryLimit so they will be deleted automatically by default. If you want to be able to add more fields to scaledJobOptions that would be a feature request. |
How long the jobs and pods stay specifically? As per official kubernetes documentation these may have adverse impact on cluster. https://kubernetes.io/docs/concepts/workloads/controllers/job/#ttl-mechanism-for-finished-jobs I tried passing below config via value file and it seems effective in cleaning up the jobs.
|
Via PR #1989, these configs and their default value added
|
Seems this issue can be closed? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
The scaledJob charts don't apply ttlSecondsAfterFinished see link and therefore jobs are stuck in completed once container is removed
chart 0.19.0
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
k8s
Docker Selenium version (tag)
4.10.0-20230607
The text was updated successfully, but these errors were encountered: