Package io.kubernetes.client.proto

Class V1Batch.JobSpec.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderType>
com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>
io.kubernetes.client.proto.V1Batch.JobSpec.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, V1Batch.JobSpecOrBuilder, Cloneable
Enclosing class:
V1Batch.JobSpec
public static final class V1Batch.JobSpec.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder> implements V1Batch.JobSpecOrBuilder
 JobSpec describes how the job execution will look like.
Protobuf type k8s.io.api.batch.v1.JobSpec

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • clear

      public V1Batch.JobSpec.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • getDefaultInstanceForType

      public V1Batch.JobSpec getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public V1Batch.JobSpec build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public V1Batch.JobSpec buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public V1Batch.JobSpec.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • setField

      public V1Batch.JobSpec.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • clearField

      public V1Batch.JobSpec.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • clearOneof

      public V1Batch.JobSpec.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • setRepeatedField

      public V1Batch.JobSpec.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • addRepeatedField

      public V1Batch.JobSpec.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • mergeFrom

      public V1Batch.JobSpec.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1Batch.JobSpec.Builder>

    • mergeFrom

      public V1Batch.JobSpec.Builder mergeFrom(V1Batch.JobSpec other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • mergeFrom

      public V1Batch.JobSpec.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1Batch.JobSpec.Builder>
      Throws:
      IOException

    • hasParallelism

      public boolean hasParallelism()
       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/
 +optional
      optional int32 parallelism = 1;
      Specified by:
      hasParallelism in interface V1Batch.JobSpecOrBuilder

    • getParallelism

      public int 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/
 +optional
      optional int32 parallelism = 1;
      Specified by:
      getParallelism in interface V1Batch.JobSpecOrBuilder

    • setParallelism

      public V1Batch.JobSpec.Builder setParallelism(int value)
       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/
 +optional
      optional int32 parallelism = 1;

    • clearParallelism

      public V1Batch.JobSpec.Builder clearParallelism()
       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/
 +optional
      optional int32 parallelism = 1;

    • hasCompletions

      public boolean hasCompletions()
       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/
 +optional
      optional int32 completions = 2;
      Specified by:
      hasCompletions in interface V1Batch.JobSpecOrBuilder

    • getCompletions

      public int 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/
 +optional
      optional int32 completions = 2;
      Specified by:
      getCompletions in interface V1Batch.JobSpecOrBuilder

    • setCompletions

      public V1Batch.JobSpec.Builder setCompletions(int value)
       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/
 +optional
      optional int32 completions = 2;

    • clearCompletions

      public V1Batch.JobSpec.Builder clearCompletions()
       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/
 +optional
      optional int32 completions = 2;

    • hasActiveDeadlineSeconds

      public boolean hasActiveDeadlineSeconds()
       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.
 +optional
      optional int64 activeDeadlineSeconds = 3;
      Specified by:
      hasActiveDeadlineSeconds in interface V1Batch.JobSpecOrBuilder

    • getActiveDeadlineSeconds

      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.
 +optional
      optional int64 activeDeadlineSeconds = 3;
      Specified by:
      getActiveDeadlineSeconds in interface V1Batch.JobSpecOrBuilder

    • setActiveDeadlineSeconds

      public V1Batch.JobSpec.Builder setActiveDeadlineSeconds(long value)
       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.
 +optional
      optional int64 activeDeadlineSeconds = 3;

    • clearActiveDeadlineSeconds

      public V1Batch.JobSpec.Builder clearActiveDeadlineSeconds()
       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.
 +optional
      optional int64 activeDeadlineSeconds = 3;

    • hasBackoffLimit

      public boolean hasBackoffLimit()
       Specifies the number of retries before marking this job failed.
 Defaults to 6
 +optional
      optional int32 backoffLimit = 7;
      Specified by:
      hasBackoffLimit in interface V1Batch.JobSpecOrBuilder

    • getBackoffLimit

      public int getBackoffLimit()
       Specifies the number of retries before marking this job failed.
 Defaults to 6
 +optional
      optional int32 backoffLimit = 7;
      Specified by:
      getBackoffLimit in interface V1Batch.JobSpecOrBuilder

    • setBackoffLimit

      public V1Batch.JobSpec.Builder setBackoffLimit(int value)
       Specifies the number of retries before marking this job failed.
 Defaults to 6
 +optional
      optional int32 backoffLimit = 7;

    • clearBackoffLimit

      public V1Batch.JobSpec.Builder clearBackoffLimit()
       Specifies the number of retries before marking this job failed.
 Defaults to 6
 +optional
      optional int32 backoffLimit = 7;

    • hasSelector

      public boolean hasSelector()
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;
      Specified by:
      hasSelector in interface V1Batch.JobSpecOrBuilder

    • getSelector

      public Meta.LabelSelector getSelector()
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;
      Specified by:
      getSelector in interface V1Batch.JobSpecOrBuilder

    • setSelector

      public V1Batch.JobSpec.Builder setSelector(Meta.LabelSelector value)
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;

    • setSelector

      public V1Batch.JobSpec.Builder setSelector(Meta.LabelSelector.Builder builderForValue)
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;

    • mergeSelector

      public V1Batch.JobSpec.Builder mergeSelector(Meta.LabelSelector value)
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;

    • clearSelector

      public V1Batch.JobSpec.Builder clearSelector()
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;

    • getSelectorBuilder

      public Meta.LabelSelector.Builder getSelectorBuilder()
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;

    • getSelectorOrBuilder

      public Meta.LabelSelectorOrBuilder getSelectorOrBuilder()
       A label query over pods that should match the pod count.
 Normally, the system sets this field for you.
 More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
 +optional
      optional .k8s.io.apimachinery.pkg.apis.meta.v1.LabelSelector selector = 4;
      Specified by:
      getSelectorOrBuilder in interface V1Batch.JobSpecOrBuilder

    • hasManualSelector

      public boolean hasManualSelector()
       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
 +optional
      optional bool manualSelector = 5;
      Specified by:
      hasManualSelector in interface V1Batch.JobSpecOrBuilder

    • getManualSelector

      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
 +optional
      optional bool manualSelector = 5;
      Specified by:
      getManualSelector in interface V1Batch.JobSpecOrBuilder

    • setManualSelector

      public V1Batch.JobSpec.Builder setManualSelector(boolean value)
       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
 +optional
      optional bool manualSelector = 5;

    • clearManualSelector

      public V1Batch.JobSpec.Builder clearManualSelector()
       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
 +optional
      optional bool manualSelector = 5;

    • hasTemplate

      public boolean hasTemplate()
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;
      Specified by:
      hasTemplate in interface V1Batch.JobSpecOrBuilder

    • getTemplate

      public V1.PodTemplateSpec getTemplate()
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;
      Specified by:
      getTemplate in interface V1Batch.JobSpecOrBuilder

    • setTemplate

      public V1Batch.JobSpec.Builder setTemplate(V1.PodTemplateSpec value)
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;

    • setTemplate

      public V1Batch.JobSpec.Builder setTemplate(V1.PodTemplateSpec.Builder builderForValue)
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;

    • mergeTemplate

      public V1Batch.JobSpec.Builder mergeTemplate(V1.PodTemplateSpec value)
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;

    • clearTemplate

      public V1Batch.JobSpec.Builder clearTemplate()
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;

    • getTemplateBuilder

      public V1.PodTemplateSpec.Builder getTemplateBuilder()
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;

    • getTemplateOrBuilder

      public V1.PodTemplateSpecOrBuilder getTemplateOrBuilder()
       Describes the pod that will be created when executing a job.
 More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
      optional .k8s.io.api.core.v1.PodTemplateSpec template = 6;
      Specified by:
      getTemplateOrBuilder in interface V1Batch.JobSpecOrBuilder

    • hasTtlSecondsAfterFinished

      public boolean hasTtlSecondsAfterFinished()
       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.
 +optional
      optional int32 ttlSecondsAfterFinished = 8;
      Specified by:
      hasTtlSecondsAfterFinished in interface V1Batch.JobSpecOrBuilder

    • getTtlSecondsAfterFinished

      public int 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.
 +optional
      optional int32 ttlSecondsAfterFinished = 8;
      Specified by:
      getTtlSecondsAfterFinished in interface V1Batch.JobSpecOrBuilder

    • setTtlSecondsAfterFinished

      public V1Batch.JobSpec.Builder setTtlSecondsAfterFinished(int value)
       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.
 +optional
      optional int32 ttlSecondsAfterFinished = 8;

    • clearTtlSecondsAfterFinished

      public V1Batch.JobSpec.Builder clearTtlSecondsAfterFinished()
       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.
 +optional
      optional int32 ttlSecondsAfterFinished = 8;

    • hasCompletionMode

      public boolean hasCompletionMode()
       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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;
      Specified by:
      hasCompletionMode in interface V1Batch.JobSpecOrBuilder

    • getCompletionMode

      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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;
      Specified by:
      getCompletionMode in interface V1Batch.JobSpecOrBuilder

    • getCompletionModeBytes

      public com.google.protobuf.ByteString getCompletionModeBytes()
       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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;
      Specified by:
      getCompletionModeBytes in interface V1Batch.JobSpecOrBuilder

    • setCompletionMode

      public V1Batch.JobSpec.Builder setCompletionMode(String value)
       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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;

    • clearCompletionMode

      public V1Batch.JobSpec.Builder clearCompletionMode()
       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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;

    • setCompletionModeBytes

      public V1Batch.JobSpec.Builder setCompletionModeBytes(com.google.protobuf.ByteString value)
       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)`.
 This field is beta-level. More completion modes can be added in the future.
 If the Job controller observes a mode that it doesn't recognize, the
 controller skips updates for the Job.
 +optional
      optional string completionMode = 9;

    • hasSuspend

      public boolean hasSuspend()
       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.
 This field is beta-level, gated by SuspendJob feature flag (enabled by
 default).
 +optional
      optional bool suspend = 10;
      Specified by:
      hasSuspend in interface V1Batch.JobSpecOrBuilder

    • getSuspend

      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.
 This field is beta-level, gated by SuspendJob feature flag (enabled by
 default).
 +optional
      optional bool suspend = 10;
      Specified by:
      getSuspend in interface V1Batch.JobSpecOrBuilder

    • setSuspend

      public V1Batch.JobSpec.Builder setSuspend(boolean value)
       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.
 This field is beta-level, gated by SuspendJob feature flag (enabled by
 default).
 +optional
      optional bool suspend = 10;

    • clearSuspend

      public V1Batch.JobSpec.Builder clearSuspend()
       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.
 This field is beta-level, gated by SuspendJob feature flag (enabled by
 default).
 +optional
      optional bool suspend = 10;

    • setUnknownFields

      public final V1Batch.JobSpec.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>

    • mergeUnknownFields

      public final V1Batch.JobSpec.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1Batch.JobSpec.Builder>