Author Avatar

Pradeep Mishra


Share post:

Kubernetes is a core component of an OpenShift Container Platform. So, the things we will discuss apply to both Kubernetes and Openshift.

The time zone feature for CronJobs was first introduced as alpha in Kubernetes version 1.24. Before that, All cron job schedule times are based on the timezone of the master node where the job is initiated.

The beta version was released in Kubernetes version 1.25. Finally, a stable version was released in Kubernetes 1.27.

Openshit with its corresponding Kubernetes versions

cron job builds on a regular job by allowing you to specifically schedule how the job should be run. Cron jobs are part of the Kubernetes API, which can be managed with oc commands like other object types.

The following is an example of a CronJob resource:

apiVersion: batch/v1beta1
kind: CronJob
  name: theCodersStop
  schedule: "*/1 * * * *"       
  timeZone: 'America/New_York' #Change timezone as per requirement
  concurrencyPolicy: "Replace"  
  startingDeadlineSeconds: 200  
  suspend: false                
  successfulJobsHistoryLimit: 3 
  failedJobsHistoryLimit: 1     
            parent: "cronjobtheCodersStop"
          - name: theCodersStop
            image: perl
            command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
          restartPolicy: OnFailure 

For CronJobs with no time zone specified, the kube-controller-manager interprets schedules relative to its local time zone.

You can specify a time zone for a CronJob by setting .spec.timeZone it to the name of a valid time zone. For example, the setting .spec.timeZone: "Etc/UTC" instructs Kubernetes to interpret the schedule relative to Coordinated Universal Time. The time zone name for the given schedule, see

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.

Specifying a timezone using CRON_TZ or TZ variables inside .spec.schedule is not officially supported (and never has been).

Starting with Kubernetes 1.29 if you try to set a schedule that includes TZ or CRON_TZ timezone specification, Kubernetes will fail to create the resource with a validation error. Updates to CronJobs already using TZ or CRON_TZ will continue to report a warning to the client.

scheduleThe schedule field for the job is specified in cron format. In this example, the job runs every minute.
concurrencyPolicyOptional: The concurrency policy specifies how the job controller treats concurrent jobs within a cron job. Only one of the following policies can be specified:
    • Allow allows multiple instances of the job to run concurrently. Allow is the default value.
    • Forbid prevents multiple instances of the job from running concurrently. Scheduled runs are skipped if the previous run has not finished.
    • Replace cancels a currently running instance of the job and replaces the job with a new instance.
startingDeadlineSecondsOptional: The starting deadline specifies a deadline (in seconds) for starting the job if a scheduled run is missed for any reason. After the deadline, the cron job does not start the job. Missed job runs are counted as failed jobs. By default, jobs have no deadline. Be aware that when this field is set, the cron job controller counts the number of missed jobs that occur in the interval between the value for the deadline and the current moment. For example, if startingDeadlineSeconds is set to 200, the controller counts the number of missed jobs in the last 200 seconds. For more information, see the limitations for cron jobs in the Kubernetes documentation for cron job concepts.
suspendOptional: The suspend field is used to prevent subsequent runs of the cron job. If set to true, then all subsequent runs are prevented from starting. By default, the value is false, and jobs are run.
successfulJobsHistoryLimitOptional: The successful jobs history limit specifies the number of finished jobs to retain. By default, three jobs are retained.
failedJobsHistoryLimitOptional: The failed jobs history limit specifies the number of failed jobs to retain. By default, one job is retained.
jobTemplateThe job template specifies the job to run. The field is similar to the job example.
labelsOptional: The labels field specifies a label to set for jobs that are started by the cron job. In this example, jobs receive the label parent=cronjobtheCodersStop.
restartPolicyOptional: The restart policy for pods that are started to run the job. The policy can be set to AlwaysOnFailure, or Never. By default, containers are always restarted. Be aware that this field does not apply to the job controller. See Known Limitations for details.

I hope you have enjoyed this post and it helped you to understand the CronJob in Kubernetes/Openshift and how it works. Please like and share and feel free to comment if you have any suggestions or feedback.


Build a module with its dependencies in a multi-module Maven project

Leave a Reply