V1DaemonSetStatus

March 28, 2026 ยท View on GitHub

DaemonSetStatus represents the current status of a daemon set.

Properties

NameTypeDescriptionNotes
collision_countintCount of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.[optional]
conditionslist[V1DaemonSetCondition]Represents the latest available observations of a DaemonSet's current state.[optional]
current_number_scheduledintThe number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
desired_number_scheduledintThe total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
number_availableintThe number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)[optional]
number_misscheduledintThe number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
number_readyintnumberReady is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running with a Ready Condition.
number_unavailableintThe number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)[optional]
observed_generationintThe most recent generation observed by the daemon set controller.[optional]
updated_number_scheduledintThe total number of nodes that are running updated daemon pod[optional]

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