Difference between revisions of "Kubernetes CronJobs"

From wikieduonline
Jump to navigation Jump to search
Line 2: Line 2:
 
* https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/
 
* https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/
  
CronJobs are meant for performing regular scheduled actions such as backups, report generation, and so on. Each of those tasks should be configured to recur indefinitely (for example: once a day / week / month); you can define the point in time within that interval when the job should start.
+
CronJobs are meant for performing regular scheduled actions such as [[backups]], [[report generation]], and so on. Each of those tasks should be configured to recur indefinitely (for example: once a day / week / month); you can define the point in time within that interval when the job should start.
  
 
== Example ==
 
== Example ==

Revision as of 13:58, 8 October 2022

Kubernetes CronJobs (previously ScheduledJobs) GA since Kubernetes 1.21 (April 2021) and Beta since Kubernetes 1.8.

CronJobs are meant for performing regular scheduled actions such as backups, report generation, and so on. Each of those tasks should be configured to recur indefinitely (for example: once a day / week / month); you can define the point in time within that interval when the job should start.

Example

https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/

apiVersion: batch/v1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: hello
            image: busybox
            imagePullPolicy: IfNotPresent
            command:
            - /bin/sh
            - -c
            - date; echo Hello from the Kubernetes cluster
          restartPolicy: OnFailure


Related

See also

Advertising: