Package io.kubernetes.client.proto

Interface V1beta1Extensions.RollingUpdateDeploymentOrBuilder

All Superinterfaces:

com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder

All Known Implementing Classes:

V1beta1Extensions.RollingUpdateDeployment, V1beta1Extensions.RollingUpdateDeployment.Builder

Enclosing class:

V1beta1Extensions

public static interface V1beta1Extensions.RollingUpdateDeploymentOrBuilder
extends com.google.protobuf.MessageOrBuilder

Method Summary

Modifier and Type	Method	Description
IntStr.IntOrString	getMaxSurge()	The maximum number of pods that can be scheduled above the desired number of pods.
IntStr.IntOrStringOrBuilder	getMaxSurgeOrBuilder()	The maximum number of pods that can be scheduled above the desired number of pods.
IntStr.IntOrString	getMaxUnavailable()	The maximum number of pods that can be unavailable during the update.
IntStr.IntOrStringOrBuilder	getMaxUnavailableOrBuilder()	The maximum number of pods that can be unavailable during the update.
boolean	hasMaxSurge()	The maximum number of pods that can be scheduled above the desired number of pods.
boolean	hasMaxUnavailable()	The maximum number of pods that can be unavailable during the update.

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

isInitialized

Methods inherited from interface com.google.protobuf.MessageOrBuilder

findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Method Details

hasMaxUnavailable

boolean hasMaxUnavailable()

 The maximum number of pods that can be unavailable during the update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 Absolute number is calculated from percentage by rounding down.
 This can not be 0 if MaxSurge is 0.
 By default, a fixed value of 1 is used.
 Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods
 immediately when the rolling update starts. Once new pods are ready, old RC
 can be scaled down further, followed by scaling up the new RC, ensuring
 that the total number of pods available at all times during the update is at
 least 70% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

getMaxUnavailable

IntStr.IntOrString getMaxUnavailable()

 The maximum number of pods that can be unavailable during the update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 Absolute number is calculated from percentage by rounding down.
 This can not be 0 if MaxSurge is 0.
 By default, a fixed value of 1 is used.
 Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods
 immediately when the rolling update starts. Once new pods are ready, old RC
 can be scaled down further, followed by scaling up the new RC, ensuring
 that the total number of pods available at all times during the update is at
 least 70% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

getMaxUnavailableOrBuilder

IntStr.IntOrStringOrBuilder getMaxUnavailableOrBuilder()

 The maximum number of pods that can be unavailable during the update.
 Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
 Absolute number is calculated from percentage by rounding down.
 This can not be 0 if MaxSurge is 0.
 By default, a fixed value of 1 is used.
 Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods
 immediately when the rolling update starts. Once new pods are ready, old RC
 can be scaled down further, followed by scaling up the new RC, ensuring
 that the total number of pods available at all times during the update is at
 least 70% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxUnavailable = 1;

hasMaxSurge

boolean hasMaxSurge()

 The maximum number of pods that can be scheduled above the desired number of
 pods.
 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.
 By default, a value of 1 is used.
 Example: when this is set to 30%, the new RC can be scaled up immediately when
 the rolling update starts, such that the total number of old and new pods do not exceed
 130% of desired pods. Once old pods have been killed,
 new RC can be scaled up further, ensuring that total number of pods running
 at any time during the update is at most 130% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

getMaxSurge

IntStr.IntOrString getMaxSurge()

 The maximum number of pods that can be scheduled above the desired number of
 pods.
 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.
 By default, a value of 1 is used.
 Example: when this is set to 30%, the new RC can be scaled up immediately when
 the rolling update starts, such that the total number of old and new pods do not exceed
 130% of desired pods. Once old pods have been killed,
 new RC can be scaled up further, ensuring that total number of pods running
 at any time during the update is at most 130% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;

getMaxSurgeOrBuilder

IntStr.IntOrStringOrBuilder getMaxSurgeOrBuilder()

 The maximum number of pods that can be scheduled above the desired number of
 pods.
 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.
 By default, a value of 1 is used.
 Example: when this is set to 30%, the new RC can be scaled up immediately when
 the rolling update starts, such that the total number of old and new pods do not exceed
 130% of desired pods. Once old pods have been killed,
 new RC can be scaled up further, ensuring that total number of pods running
 at any time during the update is at most 130% of desired pods.
 +optional
 

optional .k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;