Kubernetes Job: Difference between revisions
Line 17: | Line 17: | ||
=Kubernetes Job Manifest= | =Kubernetes Job Manifest= | ||
{{Internal|Kubernetes Job Manifest|Job Manifest}} | {{Internal|Kubernetes Job Manifest|Job Manifest}} | ||
=Parallel Execution= | |||
=Clean up Finished Jobs Automatically= | =Clean up Finished Jobs Automatically= |
Revision as of 21:09, 14 July 2023
External
Internal
Overview
A Kubernetes Job is a workload resource that can be used to start and manage Pods to successful completion.
A Pod is considered completed, and thus its execution counted against the completion counter only if finishes successfully. This counter can be configured with .spec.completions
.
The Job will attempt to restart failed Pods. The number of retires until the attempts are dropped can be configured with .spec.backoffLimit
.
Pods can be executed in parallel. The Parallel Execution section provides more details on that.
Kubernetes Job Manifest
Parallel Execution
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
...