Skip to main content
Schemaobject

io.k8s.api.batch.v1.CronJobSpec

CronJobSpec describes how the job execution will look like and when it will actually run.

Source
specs/apis__batch__v1_openapi.json
Revision
9a79c3bd90f7
Active snapshot
2a9112600697
concurrencyPolicy string
optional

Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one

failedJobsHistoryLimit integer (int32)
optional

The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1.

jobTemplate
required

Specifies the job that will be created when executing a CronJob.

schedule string
required

The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.

startingDeadlineSeconds integer (int64)
optional

Optional deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.

successfulJobsHistoryLimit integer (int32)
optional

The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.

suspend boolean
optional

This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false.

timeZone string
optional

The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time …