V1DeploymentStatus
March 28, 2026 ยท View on GitHub
DeploymentStatus is the most recently observed status of the Deployment.
Properties
| Name | Type | Description | Notes |
|---|---|---|---|
| available_replicas | int | Total number of available non-terminating pods (ready for at least minReadySeconds) targeted by this deployment. | [optional] |
| collision_count | int | Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet. | [optional] |
| conditions | list[V1DeploymentCondition] | Represents the latest available observations of a deployment's current state. | [optional] |
| observed_generation | int | The generation observed by the deployment controller. | [optional] |
| ready_replicas | int | Total number of non-terminating pods targeted by this Deployment with a Ready Condition. | [optional] |
| replicas | int | Total number of non-terminating pods targeted by this deployment (their labels match the selector). | [optional] |
| terminating_replicas | int | Total number of terminating pods targeted by this deployment. Terminating pods have a non-null .metadata.deletionTimestamp and have not yet reached the Failed or Succeeded .status.phase. This is a beta field and requires enabling DeploymentReplicaSetTerminatingReplicas feature (enabled by default). | [optional] |
| unavailable_replicas | int | Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created. | [optional] |
| updated_replicas | int | Total number of non-terminating pods targeted by this deployment that have the desired template spec. | [optional] |