Skip to main content
Version: v1.3

AdvancedCronJob

AdvancedCronJob is an enhanced version of CronJob. The original CronJob creates Job periodically according to schedule rule, but AdvancedCronJob provides template supported multpile job resources.

apiVersion: apps.kruise.io/v1alpha1
kind: AdvancedCronJob
spec:
template:

# Option 1: use jobTemplate, which is equivalent to original CronJob
jobTemplate:
# ...

# Option 2: use broadcastJobTemplate, which will create a BroadcastJob object when cron schedule triggers
broadcastJobTemplate:
# ...

# Options 3(future): ...
  • jobTemplate:create Jobs periodically, which is equivalent to original CronJob
  • broadcastJobTemplate:create BroadcastJobs periodically, which support to dispatch Jobs on every node

AdvancedCronjob

Example

apiVersion: apps.kruise.io/v1alpha1
kind: AdvancedCronJob
metadata:
name: acj-test
spec:
schedule: "*/1 * * * *"
template:
broadcastJobTemplate:
spec:
template:
spec:
containers:
- name: pi
image: perl
command: ["perl", "-Mbignum=bpi", "-wle", "print bpi(2000)"]
restartPolicy: Never
completionPolicy:
type: Always
ttlSecondsAfterFinished: 30

The YAML below defines an AdvancedCronJob. It will create a BroadcastJob every minute, which will run a job on every node.

Time zones

All CronJob schedule: times are based on the timezone of the kruise-controller-manager by default, which means the timezone set for the kruise-controller-manager container determines the timezone that the cron job controller uses.

FEATURE STATE: Kruise v1.3.0

However, we have introduce a spec.timeZone field in v1.3.0. You can set it to the name of a valid time zone name. For example, setting spec.timeZone: "Etc/UTC" instructs Kruise to interpret the schedule relative to Coordinated Universal Time.

A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.