Struct RollingDeploymentStrategyParams

pub struct RollingDeploymentStrategyParams {
    pub interval_seconds: Option<i64>,
    pub max_surge: Option<IntOrString>,
    pub max_unavailable: Option<IntOrString>,
    pub post: Option<LifecycleHook>,
    pub pre: Option<LifecycleHook>,
    pub timeout_seconds: Option<i64>,
    pub update_period_seconds: Option<i64>,
}

RollingDeploymentStrategyParams are the input to the Rolling deployment strategy.

Fields

interval_seconds: Option<i64>

IntervalSeconds is the time to wait between polling deployment status after update. If the value is nil, a default will be used.

max_surge: Option<IntOrString>

MaxSurge is the maximum number of pods that can be scheduled above the original number of pods. Value can be an absolute number (ex: 5) or a percentage of total pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up.

This cannot be 0 if MaxUnavailable is 0. By default, 25% is used.

Example: when this is set to 30%, the new RC can be scaled up by 30% immediately when the rolling update starts. 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 atmost 130% of original pods.

max_unavailable: Option<IntOrString>

MaxUnavailable is the maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total pods at the start of update (ex: 10%). Absolute number is calculated from percentage by rounding down.

This cannot be 0 if MaxSurge is 0. By default, 25% is used.

Example: when this is set to 30%, the old RC can be scaled down by 30% 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 at least 70% of original number of pods are available at all times during the update.

post: Option<LifecycleHook>

Post is a lifecycle hook which is executed after the strategy has finished all deployment logic. All LifecycleHookFailurePolicy values are supported.

pre: Option<LifecycleHook>

Pre is a lifecycle hook which is executed before the deployment process begins. All LifecycleHookFailurePolicy values are supported.

timeout_seconds: Option<i64>

TimeoutSeconds is the time to wait for updates before giving up. If the value is nil, a default will be used.

update_period_seconds: Option<i64>

UpdatePeriodSeconds is the time to wait between individual pod updates. If the value is nil, a default will be used.

Trait Implementations

impl Clone for RollingDeploymentStrategyParams

fn clone(&self) -> RollingDeploymentStrategyParams

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RollingDeploymentStrategyParams

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RollingDeploymentStrategyParams

fn default() -> RollingDeploymentStrategyParams

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for RollingDeploymentStrategyParams

fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>

where D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for RollingDeploymentStrategyParams

fn eq(&self, other: &RollingDeploymentStrategyParams) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for RollingDeploymentStrategyParams

fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>

where S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for RollingDeploymentStrategyParams