Struct k8s_openapi::api::batch::v1::JobStatus

pub struct JobStatus {
    pub active: Option<i32>,
    pub completed_indexes: Option<String>,
    pub completion_time: Option<Time>,
    pub conditions: Option<Vec<JobCondition>>,
    pub failed: Option<i32>,
    pub failed_indexes: Option<String>,
    pub ready: Option<i32>,
    pub start_time: Option<Time>,
    pub succeeded: Option<i32>,
    pub terminating: Option<i32>,
    pub uncounted_terminated_pods: Option<UncountedTerminatedPods>,
}

JobStatus represents the current state of a Job.

Fields

active: Option<i32>

The number of pending and running pods which are not terminating (without a deletionTimestamp). The value is zero for finished jobs.

completed_indexes: Option<String>

completedIndexes holds the completed indexes when .spec.completionMode = “Indexed” in a text format. The indexes are represented as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the completed indexes are 1, 3, 4, 5 and 7, they are represented as “1,3-5,7”.

completion_time: Option<Time>

Represents time when the job was completed. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC. The completion time is set when the job finishes successfully, and only then. The value cannot be updated or removed. The value indicates the same or later point in time as the startTime field.

conditions: Option<Vec<JobCondition>>

The latest available observations of an object’s current state. When a Job fails, one of the conditions will have type “Failed” and status true. When a Job is suspended, one of the conditions will have type “Suspended” and status true; when the Job is resumed, the status of this condition will become false. When a Job is completed, one of the conditions will have type “Complete” and status true.

A job is considered finished when it is in a terminal condition, either “Complete” or “Failed”. A Job cannot have both the “Complete” and “Failed” conditions. Additionally, it cannot be in the “Complete” and “FailureTarget” conditions. The “Complete”, “Failed” and “FailureTarget” conditions cannot be disabled.

More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/

failed: Option<i32>

The number of pods which reached phase Failed. The value increases monotonically.

failed_indexes: Option<String>

FailedIndexes holds the failed indexes when spec.backoffLimitPerIndex is set. The indexes are represented in the text format analogous as for the completedIndexes field, ie. they are kept as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the failed indexes are 1, 3, 4, 5 and 7, they are represented as “1,3-5,7”. The set of failed indexes cannot overlap with the set of completed indexes.

This field is beta-level. It can be used when the JobBackoffLimitPerIndex feature gate is enabled (enabled by default).

ready: Option<i32>

The number of pods which have a Ready condition.

start_time: Option<Time>

Represents time when the job controller started processing a job. When a Job is created in the suspended state, this field is not set until the first time it is resumed. This field is reset every time a Job is resumed from suspension. It is represented in RFC3339 form and is in UTC.

Once set, the field can only be removed when the job is suspended. The field cannot be modified while the job is unsuspended or finished.

succeeded: Option<i32>

The number of pods which reached phase Succeeded. The value increases monotonically for a given spec. However, it may decrease in reaction to scale down of elastic indexed jobs.

terminating: Option<i32>

The number of pods which are terminating (in phase Pending or Running and have a deletionTimestamp).

This field is beta-level. The job controller populates the field when the feature gate JobPodReplacementPolicy is enabled (enabled by default).

uncounted_terminated_pods: Option<UncountedTerminatedPods>

uncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn’t yet accounted for in the status counters.

The job controller creates pods with a finalizer. When a pod terminates (succeeded or failed), the controller does three steps to account for it in the job status:

1. Add the pod UID to the arrays in this field. 2. Remove the pod finalizer. 3. Remove the pod UID from the arrays while increasing the corresponding counter.

Old jobs might not be tracked using this field, in which case the field remains null. The structure is empty for finished jobs.

Trait Implementations

impl Clone for JobStatus

fn clone(&self) -> JobStatus

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for JobStatus

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

Formats the value using the given formatter.

impl DeepMerge for JobStatus

fn merge_from(&mut self, other: Self)

Merge other into self.

impl Default for JobStatus

fn default() -> JobStatus

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for JobStatus

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

where D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for JobStatus

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

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

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

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

impl Serialize for JobStatus

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 JobStatus