Struct openshift_openapi::api::apps::v1::DeploymentConfigSpec

pub struct DeploymentConfigSpec {
    pub min_ready_seconds: Option<i32>,
    pub paused: Option<bool>,
    pub replicas: Option<i32>,
    pub revision_history_limit: Option<i32>,
    pub selector: Option<BTreeMap<String, String>>,
    pub strategy: Option<DeploymentStrategy>,
    pub template: Option<PodTemplateSpec>,
    pub test: Option<bool>,
    pub triggers: Option<Vec<DeploymentTriggerPolicy>>,
}

DeploymentConfigSpec represents the desired state of the deployment.

Fields

min_ready_seconds: Option<i32>

MinReadySeconds is the minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)

paused: Option<bool>

Paused indicates that the deployment config is paused resulting in no new deployments on template changes or changes in the template caused by other triggers.

replicas: Option<i32>

Replicas is the number of desired replicas.

revision_history_limit: Option<i32>

RevisionHistoryLimit is the number of old ReplicationControllers to retain to allow for rollbacks. This field is a pointer to allow for differentiation between an explicit zero and not specified. Defaults to 10. (This only applies to DeploymentConfigs created via the new group API resource, not the legacy resource.)

selector: Option<BTreeMap<String, String>>

Selector is a label query over pods that should match the Replicas count.

strategy: Option<DeploymentStrategy>

Strategy describes how a deployment is executed.

template: Option<PodTemplateSpec>

Template is the object that describes the pod that will be created if insufficient replicas are detected.

test: Option<bool>

Test ensures that this deployment config will have zero replicas except while a deployment is running. This allows the deployment config to be used as a continuous deployment test - triggering on images, running the deployment, and then succeeding or failing. Post strategy hooks and After actions can be used to integrate successful deployment with an action.

triggers: Option<Vec<DeploymentTriggerPolicy>>

Triggers determine how updates to a DeploymentConfig result in new deployments. If no triggers are defined, a new deployment can only occur as a result of an explicit client update to the DeploymentConfig with a new LatestVersion. If null, defaults to having a config change trigger.

Trait Implementations

impl Clone for DeploymentConfigSpec

fn clone(&self) -> DeploymentConfigSpec

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for DeploymentConfigSpec

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

Formats the value using the given formatter.

impl Default for DeploymentConfigSpec

fn default() -> DeploymentConfigSpec

Returns the "default value" for a type.

impl<'de> Deserialize<'de> for DeploymentConfigSpec

fn deserialize<D>(deserializer: D) -> Result<Self, D::Error> where
    D: Deserializer<'de>, 

Deserialize this value from the given Serde deserializer.

impl PartialEq<DeploymentConfigSpec> for DeploymentConfigSpec

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

This method tests for self and other values to be equal, and is used by ==.

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

This method tests for !=.

impl Serialize for DeploymentConfigSpec

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 DeploymentConfigSpec