Package io.kubernetes.client.proto

Class V1Apps.RollingUpdateDaemonSet.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderType>
com.google.protobuf.GeneratedMessageV3.Builder<V1Apps.RollingUpdateDaemonSet.Builder>
io.kubernetes.client.proto.V1Apps.RollingUpdateDaemonSet.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, V1Apps.RollingUpdateDaemonSetOrBuilder, Cloneable
Enclosing class:
V1Apps.RollingUpdateDaemonSet
public static final class V1Apps.RollingUpdateDaemonSet.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<V1Apps.RollingUpdateDaemonSet.Builder> implements V1Apps.RollingUpdateDaemonSetOrBuilder
 Spec to control the desired behavior of daemon set rolling update.
Protobuf type k8s.io.api.apps.v1.RollingUpdateDaemonSet

  • 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<V1Apps.RollingUpdateDaemonSet.Builder>

    • clear

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • getDefaultInstanceForType

      public V1Apps.RollingUpdateDaemonSet getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

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

    • buildPartial

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

    • clone

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • setField

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • clearField

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • clearOneof

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • setRepeatedField

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • addRepeatedField

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • mergeFrom

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • mergeFrom

      public V1Apps.RollingUpdateDaemonSet.Builder mergeFrom(V1Apps.RollingUpdateDaemonSet other)

    • isInitialized

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

    • mergeFrom

      public V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>
      Throws:
      IOException

    • hasMaxUnavailable

      public boolean hasMaxUnavailable()
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;
      Specified by:
      hasMaxUnavailable in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • getMaxUnavailable

      public IntStr.IntOrString getMaxUnavailable()
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;
      Specified by:
      getMaxUnavailable in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • setMaxUnavailable

      public V1Apps.RollingUpdateDaemonSet.Builder setMaxUnavailable(IntStr.IntOrString value)
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

    • setMaxUnavailable

      public V1Apps.RollingUpdateDaemonSet.Builder setMaxUnavailable(IntStr.IntOrString.Builder builderForValue)
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

    • mergeMaxUnavailable

      public V1Apps.RollingUpdateDaemonSet.Builder mergeMaxUnavailable(IntStr.IntOrString value)
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

    • clearMaxUnavailable

      public V1Apps.RollingUpdateDaemonSet.Builder clearMaxUnavailable()
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

    • getMaxUnavailableBuilder

      public IntStr.IntOrString.Builder getMaxUnavailableBuilder()
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

    • getMaxUnavailableOrBuilder

      public IntStr.IntOrStringOrBuilder getMaxUnavailableOrBuilder()
       The maximum number of DaemonSet pods that can be unavailable during the
 update. Value can be an absolute number (ex: 5) or a percentage of total
 number of DaemonSet pods at the start of the update (ex: 10%). Absolute
 number is calculated from percentage by rounding up.
 This cannot be 0 if MaxSurge is 0
 Default value is 1.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their pods stopped for an update at any given time. The update
 starts by stopping at most 30% of those DaemonSet pods and then brings
 up new DaemonSet pods in their place. Once the new pods are available,
 it then proceeds onto other DaemonSet pods, thus ensuring that at least
 70% of original number of DaemonSet pods are available at all times during
 the update.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;
      Specified by:
      getMaxUnavailableOrBuilder in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • hasMaxSurge

      public boolean hasMaxSurge()
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
      Specified by:
      hasMaxSurge in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • getMaxSurge

      public IntStr.IntOrString getMaxSurge()
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
      Specified by:
      getMaxSurge in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • setMaxSurge

      public V1Apps.RollingUpdateDaemonSet.Builder setMaxSurge(IntStr.IntOrString value)
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

    • setMaxSurge

      public V1Apps.RollingUpdateDaemonSet.Builder setMaxSurge(IntStr.IntOrString.Builder builderForValue)
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

    • mergeMaxSurge

      public V1Apps.RollingUpdateDaemonSet.Builder mergeMaxSurge(IntStr.IntOrString value)
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

    • clearMaxSurge

      public V1Apps.RollingUpdateDaemonSet.Builder clearMaxSurge()
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

    • getMaxSurgeBuilder

      public IntStr.IntOrString.Builder getMaxSurgeBuilder()
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

    • getMaxSurgeOrBuilder

      public IntStr.IntOrStringOrBuilder getMaxSurgeOrBuilder()
       The maximum number of nodes with an existing available DaemonSet pod that
 can have an updated DaemonSet pod during during an update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 This can not be 0 if MaxUnavailable is 0.
 Absolute number is calculated from percentage by rounding up to a minimum of 1.
 Default value is 0.
 Example: when this is set to 30%, at most 30% of the total number of nodes
 that should be running the daemon pod (i.e. status.desiredNumberScheduled)
 can have their a new pod created before the old pod is marked as deleted.
 The update starts by launching new pods on 30% of nodes. Once an updated
 pod is available (Ready for at least minReadySeconds) the old DaemonSet pod
 on that node is marked deleted. If the old pod becomes unavailable for any
 reason (Ready transitions to false, is evicted, or is drained) an updated
 pod is immediatedly created on that node without considering surge limits.
 Allowing surge implies the possibility that the resources consumed by the
 daemonset on any given node can double if the readiness check fails, and
 so resource intensive daemonsets should take into account that they may
 cause evictions during disruption.
 This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate.
 +optional
      optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
      Specified by:
      getMaxSurgeOrBuilder in interface V1Apps.RollingUpdateDaemonSetOrBuilder

    • setUnknownFields

      public final V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>

    • mergeUnknownFields

      public final V1Apps.RollingUpdateDaemonSet.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<V1Apps.RollingUpdateDaemonSet.Builder>