Class V1CronJobSpec
java.lang.Object
io.kubernetes.client.openapi.models.V1CronJobSpec
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen",
date="2024-02-02T21:37:40.170033Z[Etc/UTC]")
public class V1CronJobSpec
extends Object
CronJobSpec describes how the job execution will look like and when it will actually run.
-
Field Summary
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionconcurrencyPolicy
(String concurrencyPolicy) boolean
failedJobsHistoryLimit
(Integer failedJobsHistoryLimit) Specifies how to treat concurrent executions of a Job.The number of failed finished jobs to retain.Get jobTemplateThe schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.Optional deadline in seconds for starting the job if it misses scheduled time for any reason.The number of successful finished jobs to retain.This flag tells the controller to suspend subsequent executions, it does not apply to already started executions.The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones.int
hashCode()
jobTemplate
(V1JobTemplateSpec jobTemplate) void
setConcurrencyPolicy
(String concurrencyPolicy) void
setFailedJobsHistoryLimit
(Integer failedJobsHistoryLimit) void
setJobTemplate
(V1JobTemplateSpec jobTemplate) void
setSchedule
(String schedule) void
setStartingDeadlineSeconds
(Long startingDeadlineSeconds) void
setSuccessfulJobsHistoryLimit
(Integer successfulJobsHistoryLimit) void
setSuspend
(Boolean suspend) void
setTimeZone
(String timeZone) startingDeadlineSeconds
(Long startingDeadlineSeconds) successfulJobsHistoryLimit
(Integer successfulJobsHistoryLimit) toString()
-
Field Details
-
SERIALIZED_NAME_CONCURRENCY_POLICY
- See Also:
-
SERIALIZED_NAME_FAILED_JOBS_HISTORY_LIMIT
- See Also:
-
SERIALIZED_NAME_JOB_TEMPLATE
- See Also:
-
SERIALIZED_NAME_SCHEDULE
- See Also:
-
SERIALIZED_NAME_STARTING_DEADLINE_SECONDS
- See Also:
-
SERIALIZED_NAME_SUCCESSFUL_JOBS_HISTORY_LIMIT
- See Also:
-
SERIALIZED_NAME_SUSPEND
- See Also:
-
SERIALIZED_NAME_TIME_ZONE
- See Also:
-
-
Constructor Details
-
V1CronJobSpec
public V1CronJobSpec()
-
-
Method Details
-
concurrencyPolicy
-
getConcurrencyPolicy
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- Returns:
- concurrencyPolicy
-
setConcurrencyPolicy
-
failedJobsHistoryLimit
-
getFailedJobsHistoryLimit
The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1.- Returns:
- failedJobsHistoryLimit
-
setFailedJobsHistoryLimit
-
jobTemplate
-
getJobTemplate
Get jobTemplate- Returns:
- jobTemplate
-
setJobTemplate
-
schedule
-
getSchedule
The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.- Returns:
- schedule
-
setSchedule
-
startingDeadlineSeconds
-
getStartingDeadlineSeconds
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.- Returns:
- startingDeadlineSeconds
-
setStartingDeadlineSeconds
-
successfulJobsHistoryLimit
-
getSuccessfulJobsHistoryLimit
The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.- Returns:
- successfulJobsHistoryLimit
-
setSuccessfulJobsHistoryLimit
-
suspend
-
getSuspend
This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false.- Returns:
- suspend
-
setSuspend
-
timeZone
-
getTimeZone
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- Returns:
- timeZone
-
setTimeZone
-
equals
-
hashCode
public int hashCode() -
toString
-