Package io.kubernetes.client.openapi.models

Class V1JobSpec

java.lang.Object
io.kubernetes.client.openapi.models.V1JobSpec
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2022-12-05T08:14:34.919Z[Etc/UTC]") public class V1JobSpec extends Object
JobSpec describes how the job execution will look like.

  • Field Details

  • Constructor Details

    • V1JobSpec

      public V1JobSpec()

  • Method Details

    • activeDeadlineSeconds

      public V1JobSpec activeDeadlineSeconds(Long activeDeadlineSeconds)

    • getActiveDeadlineSeconds

      @Nullable public Long getActiveDeadlineSeconds()
      Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. If a Job is suspended (at creation or through an update), this timer will effectively be stopped and reset when the Job is resumed again.
      Returns:
      activeDeadlineSeconds

    • setActiveDeadlineSeconds

      public void setActiveDeadlineSeconds(Long activeDeadlineSeconds)

    • backoffLimit

      public V1JobSpec backoffLimit(Integer backoffLimit)

    • getBackoffLimit

      @Nullable public Integer getBackoffLimit()
      Specifies the number of retries before marking this job failed. Defaults to 6
      Returns:
      backoffLimit

    • setBackoffLimit

      public void setBackoffLimit(Integer backoffLimit)

    • completionMode

      public V1JobSpec completionMode(String completionMode)

    • getCompletionMode

      @Nullable public String getCompletionMode()
      CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`. `NonIndexed` means that the Job is considered complete when there have been .spec.completions successfully completed Pods. Each Pod completion is homologous to each other. `Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5. In addition, The Pod name takes the form `$(job-name)-$(index)-$(random-string)`, the Pod hostname takes the form `$(job-name)-$(index)`. More completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, which is possible during upgrades due to version skew, the controller skips updates for the Job.
      Returns:
      completionMode

    • setCompletionMode

      public void setCompletionMode(String completionMode)

    • completions

      public V1JobSpec completions(Integer completions)

    • getCompletions

      @Nullable public Integer getCompletions()
      Specifies the desired number of successfully finished pods the job should be run with. Setting to nil means that the success of any pod signals the success of all pods, and allows parallelism to have any positive value. Setting to 1 means that parallelism is limited to 1 and the success of that pod signals the success of the job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      Returns:
      completions

    • setCompletions

      public void setCompletions(Integer completions)

    • manualSelector

      public V1JobSpec manualSelector(Boolean manualSelector)

    • getManualSelector

      @Nullable public Boolean getManualSelector()
      manualSelector controls generation of pod labels and pod selectors. Leave `manualSelector` unset unless you are certain what you are doing. When false or unset, the system pick labels unique to this job and appends those labels to the pod template. When true, the user is responsible for picking unique labels and specifying the selector. Failure to pick a unique label may cause this and other jobs to not function correctly. However, You may see `manualSelector=true` in jobs that were created with the old `extensions/v1beta1` API. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector
      Returns:
      manualSelector

    • setManualSelector

      public void setManualSelector(Boolean manualSelector)

    • parallelism

      public V1JobSpec parallelism(Integer parallelism)

    • getParallelism

      @Nullable public Integer getParallelism()
      Specifies the maximum desired number of pods the job should run at any given time. The actual number of pods running in steady state will be less than this number when ((.spec.completions - .status.successful) < .spec.parallelism), i.e. when the work left to do is less than max parallelism. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      Returns:
      parallelism

    • setParallelism

      public void setParallelism(Integer parallelism)

    • podFailurePolicy

      public V1JobSpec podFailurePolicy(V1PodFailurePolicy podFailurePolicy)

    • getPodFailurePolicy

      @Nullable public V1PodFailurePolicy getPodFailurePolicy()
      Get podFailurePolicy
      Returns:
      podFailurePolicy

    • setPodFailurePolicy

      public void setPodFailurePolicy(V1PodFailurePolicy podFailurePolicy)

    • selector

      public V1JobSpec selector(V1LabelSelector selector)

    • getSelector

      @Nullable public V1LabelSelector getSelector()
      Get selector
      Returns:
      selector

    • setSelector

      public void setSelector(V1LabelSelector selector)

    • suspend

      public V1JobSpec suspend(Boolean suspend)

    • getSuspend

      @Nullable public Boolean getSuspend()
      Suspend specifies whether the Job controller should create Pods or not. If a Job is created with suspend set to true, no Pods are created by the Job controller. If a Job is suspended after creation (i.e. the flag goes from false to true), the Job controller will delete all active Pods associated with this Job. Users must design their workload to gracefully handle this. Suspending a Job will reset the StartTime field of the Job, effectively resetting the ActiveDeadlineSeconds timer too. Defaults to false.
      Returns:
      suspend

    • setSuspend

      public void setSuspend(Boolean suspend)

    • template

      public V1JobSpec template(V1PodTemplateSpec template)

    • getTemplate

      public V1PodTemplateSpec getTemplate()
      Get template
      Returns:
      template

    • setTemplate

      public void setTemplate(V1PodTemplateSpec template)

    • ttlSecondsAfterFinished

      public V1JobSpec ttlSecondsAfterFinished(Integer ttlSecondsAfterFinished)

    • getTtlSecondsAfterFinished

      @Nullable public Integer getTtlSecondsAfterFinished()
      ttlSecondsAfterFinished limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. When the Job is being deleted, its lifecycle guarantees (e.g. finalizers) will be honored. If this field is unset, the Job won't be automatically deleted. If this field is set to zero, the Job becomes eligible to be deleted immediately after it finishes.
      Returns:
      ttlSecondsAfterFinished

    • setTtlSecondsAfterFinished

      public void setTtlSecondsAfterFinished(Integer ttlSecondsAfterFinished)

    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object

    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object

    • toString

      public String toString()
      Overrides:
      toString in class Object