Difference between revisions of "Kubernetes CronJobs"
Jump to navigation
Jump to search
| (4 intermediate revisions by 2 users not shown) | |||
| 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 == | ||
https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/ | https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/ | ||
[[apiVersion:]] batch/v1 | [[apiVersion:]] batch/v1 | ||
| − | [[kind:]] | + | [[kind: CronJob]] |
[[metadata:]] | [[metadata:]] | ||
name: hello | name: hello | ||
| Line 18: | Line 18: | ||
containers: | containers: | ||
- name: hello | - name: hello | ||
| − | image: [[busybox]] | + | [[image]]: [[busybox]] |
imagePullPolicy: IfNotPresent | imagePullPolicy: IfNotPresent | ||
command: | command: | ||
| Line 25: | Line 25: | ||
- date; echo Hello from the Kubernetes cluster | - date; echo Hello from the Kubernetes cluster | ||
restartPolicy: OnFailure | restartPolicy: OnFailure | ||
| − | |||
== Related == | == Related == | ||
| Line 32: | Line 31: | ||
* [[Jobs (Kubernetes)]] | * [[Jobs (Kubernetes)]] | ||
* [[Kubernetes scheduling]] | * [[Kubernetes scheduling]] | ||
| + | * [[Cronitor]] | ||
== See also == | == See also == | ||
Latest revision as of 19:09, 18 November 2023
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[edit]
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[edit]
kind: Job,kubectl get jobskind: CronJob,kubectl get cronjob- Jobs (Kubernetes)
- Kubernetes scheduling
- Cronitor
See also[edit]
- CronJobs (Kubernetes), Understand Jobs and CronJobs,
kind: Job,job-controller - Kubernetes Workloads:
Deployment,ReplicaSet, StatefulSet, DaemonSets, Job, CronJob,.apps/ cron,crontab,systemctl list-timers, anacron, Kubernetes scheduler, Systemd services,CronJobsStack,cron.schedule,crontab -l,0x004b,at, /etc/cron.deny, /etc/cron.allow, /etc/crontab, /var/spool/cron/crontabs/
Advertising:
