Kubernetes Job: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
{{External|https://kubernetes.io/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically}} | {{External|https://kubernetes.io/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically}} | ||
Jobs that have finished, either "Complete" or "Failed" can be automatically be deleted by using the TTL mechanism provided by the [TTL Controller ]. Set the <code>.spec.ttlSecondsAfterFinished</code> field in the job manifest | Jobs that have finished, either "Complete" or "Failed" can be automatically be deleted by using the TTL mechanism provided by the [TTL Controller ]. Set the <code>.spec.ttlSecondsAfterFinished</code> field in the job manifest. If the field is set to 0, the Job will be eligible to be automatically deleted immediately after it finishes. | ||
<syntaxhighlight lang='yaml'> | <syntaxhighlight lang='yaml'> | ||
Revision as of 03:26, 30 April 2022
Internal
Overview
Clean up Finished Jobs Automatically
Jobs that have finished, either "Complete" or "Failed" can be automatically be deleted by using the TTL mechanism provided by the [TTL Controller ]. Set the .spec.ttlSecondsAfterFinished field in the job manifest. If the field is set to 0, the Job will be eligible to be automatically deleted immediately after it finishes.
apiVersion: batch/v1
kind: Job
spec:
ttlSecondsAfterFinished: 100
...