Skip to content

Latest commit

 

History

History
18 lines (14 loc) · 2.45 KB

V1CronJobSpec.md

File metadata and controls

18 lines (14 loc) · 2.45 KB

V1CronJobSpec

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

Properties

Name Type Description Notes
concurrency_policy str 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 [optional]
failed_jobs_history_limit int The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1. [optional]
job_template V1JobTemplateSpec
schedule str The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.
starting_deadline_seconds int 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. [optional]
successful_jobs_history_limit int The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3. [optional]
suspend bool This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false. [optional]
time_zone str 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 zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones [optional]

[Back to Model list] [Back to API list] [Back to README]