This repository has been archived on 2025-01-23. You can view files and clone it, but cannot push or open issues or pull requests.
traefik-certmanager/kubernetes/docs/V1DeploymentStatus.md
Tom Neuber 9129813244
All checks were successful
ci/woodpecker/push/build Pipeline was successful
ci/woodpecker/push/deploy Pipeline was successful
fix(kubernetes): temporary solution for updated k8s python client
2025-01-05 00:33:58 +01:00

1.7 KiB

V1DeploymentStatus

DeploymentStatus is the most recently observed status of the Deployment.

Properties

Name Type Description Notes
available_replicas int Total number of available 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 readyReplicas is the number of pods targeted by this Deployment with a Ready Condition. [optional]
replicas int Total number of non-terminated pods targeted by this deployment (their labels match the selector). [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-terminated pods targeted by this deployment that have the desired template spec. [optional]

[Back to Model list] [Back to API list] [Back to README]