kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Recommend using TTL field in job 

Recommend using ttlSecondsAfterFinished in the job spec so that the pod deletion can be guaranteed when jobs get deleted.
This commit is contained in:
Ravi Gudimetla 2021-08-19 16:59:53 -04:00 committed by GitHub
parent dd2f06f64a
commit 6c50bc639f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/en/docs/concepts/workloads/controllers/job.md
View File

@ -342,6 +342,16 @@ If the field is set to `0`, the Job will be eligible to be automatically deleted
immediately after it finishes. If the field is unset, this Job won't be cleaned immediately after it finishes. If the field is unset, this Job won't be cleaned
up by the TTL controller after it finishes. up by the TTL controller after it finishes.
{{< note >}}
It is recommended to set `ttlSecondsAfterFinished` field because unmanaged jobs
(jobs not created via high level controllers like cronjobs) have a default deletion
policy of `orphanDependents` causing pods created by this job to be left around.
Even though podgc collector eventually deletes these lingering pods, sometimes these
lingering pods may cause cluster performance degradation or in worst case cause the
cluster to go down.
{{< /note >}}
## Job patterns ## Job patterns
The Job object can be used to support reliable parallel execution of Pods. The Job object is not The Job object can be used to support reliable parallel execution of Pods. The Job object is not