Class V1CronJobSpec
java.lang.Object
io.micronaut.kubernetes.client.openapi.model.V1CronJobSpec
@Generated("io.micronaut.openapi.generator.JavaMicronautClientCodegen")
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) Set concurrencyPolicy in a chainable fashion.boolean
failedJobsHistoryLimit
(Integer failedJobsHistoryLimit) Set failedJobsHistoryLimit in a chainable fashion.Specifies how to treat concurrent executions of a Job.The number of failed finished jobs to retain.The 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) Set jobTemplate in a chainable fashion.Set schedule in a chainable fashion.void
setConcurrencyPolicy
(String concurrencyPolicy) Set the concurrencyPolicy property valuevoid
setFailedJobsHistoryLimit
(Integer failedJobsHistoryLimit) Set the failedJobsHistoryLimit property valuevoid
setJobTemplate
(V1JobTemplateSpec jobTemplate) Set the jobTemplate property valuevoid
setSchedule
(String schedule) Set the schedule property valuevoid
setStartingDeadlineSeconds
(Long startingDeadlineSeconds) Set the startingDeadlineSeconds property valuevoid
setSuccessfulJobsHistoryLimit
(Integer successfulJobsHistoryLimit) Set the successfulJobsHistoryLimit property valuevoid
setSuspend
(Boolean suspend) Set the suspend property valuevoid
setTimeZone
(String timeZone) Set the timeZone property valuestartingDeadlineSeconds
(Long startingDeadlineSeconds) Set startingDeadlineSeconds in a chainable fashion.successfulJobsHistoryLimit
(Integer successfulJobsHistoryLimit) Set successfulJobsHistoryLimit in a chainable fashion.Set suspend in a chainable fashion.Set timeZone in a chainable fashion.toString()
-
Field Details
-
JSON_PROPERTY_JOB_TEMPLATE
- See Also:
-
JSON_PROPERTY_SCHEDULE
- See Also:
-
JSON_PROPERTY_CONCURRENCY_POLICY
- See Also:
-
JSON_PROPERTY_FAILED_JOBS_HISTORY_LIMIT
- See Also:
-
JSON_PROPERTY_STARTING_DEADLINE_SECONDS
- See Also:
-
JSON_PROPERTY_SUCCESSFUL_JOBS_HISTORY_LIMIT
- See Also:
-
JSON_PROPERTY_SUSPEND
- See Also:
-
JSON_PROPERTY_TIME_ZONE
- See Also:
-
-
Constructor Details
-
V1CronJobSpec
-
-
Method Details
-
getJobTemplate
- Returns:
- the jobTemplate property value
-
setJobTemplate
Set the jobTemplate property value- Parameters:
jobTemplate
- property value to set
-
jobTemplate
Set jobTemplate in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
getSchedule
The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.- Returns:
- the schedule property value
-
setSchedule
Set the schedule property value- Parameters:
schedule
- property value to set
-
schedule
Set schedule in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
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:
- the concurrencyPolicy property value
-
setConcurrencyPolicy
Set the concurrencyPolicy property value- Parameters:
concurrencyPolicy
- property value to set
-
concurrencyPolicy
Set concurrencyPolicy in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
getFailedJobsHistoryLimit
The number of failed finished jobs to retain. Value must be non-negative integer. Defaults to 1.- Returns:
- the failedJobsHistoryLimit property value
-
setFailedJobsHistoryLimit
Set the failedJobsHistoryLimit property value- Parameters:
failedJobsHistoryLimit
- property value to set
-
failedJobsHistoryLimit
Set failedJobsHistoryLimit in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
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:
- the startingDeadlineSeconds property value
-
setStartingDeadlineSeconds
Set the startingDeadlineSeconds property value- Parameters:
startingDeadlineSeconds
- property value to set
-
startingDeadlineSeconds
Set startingDeadlineSeconds in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
getSuccessfulJobsHistoryLimit
The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.- Returns:
- the successfulJobsHistoryLimit property value
-
setSuccessfulJobsHistoryLimit
Set the successfulJobsHistoryLimit property value- Parameters:
successfulJobsHistoryLimit
- property value to set
-
successfulJobsHistoryLimit
Set successfulJobsHistoryLimit in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
getSuspend
This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false.- Returns:
- the suspend property value
-
setSuspend
Set the suspend property value- Parameters:
suspend
- property value to set
-
suspend
Set suspend in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
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:
- the timeZone property value
-
setTimeZone
Set the timeZone property value- Parameters:
timeZone
- property value to set
-
timeZone
Set timeZone in a chainable fashion.- Returns:
- The same instance of V1CronJobSpec for chaining.
-
equals
-
hashCode
public int hashCode() -
toString
-