-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Job objects are not cleaned up #64470
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/feature
Categorizes issue or PR as related to a new feature.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
Comments
Was planning to solve this problem in a generic way: kubernetes/community#2287 @kubernetes/sig-apps-feature-requests |
This was referenced Jul 18, 2018
k8s-github-robot
pushed a commit
that referenced
this issue
Sep 5, 2018
Automatic merge from submit-queue (batch tested with PRs 66840, 68159). If you want to cherry-pick this change to another branch, please follow the instructions here: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md. TTL for cleaning up Jobs after they finish **What this PR does / why we need it**: kubernetes/enhancements#592 **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes #64470 For kubernetes/enhancements#592 **Special notes for your reviewer**: @kubernetes/sig-apps-pr-reviews **Release note**: ```release-note Add a TTL machenism to clean up Jobs after they finish. ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/feature
Categorizes issue or PR as related to a new feature.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
/kind bug
/sig apps
It's easy to make jobs and forget to delete them. If you make enough of them, you can overload a control plane (which is typically sized to support the number of nodes and not an arbitrarily high number of jobs).
We have a "podgc" for deleting terminated pods if too many of them build up, so there is precedent.
The text was updated successfully, but these errors were encountered: