DaemonSetStatus represents the current status of a daemon set.
- Value Params
- collisionCount
Count 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.
- conditions
Represents the latest available observations of a DaemonSet's current state.
- currentNumberScheduled
The 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/
- desiredNumberScheduled
The 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/
- numberAvailable
The 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)
- numberMisscheduled
The 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/
- numberReady
The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.
- numberUnavailable
The 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)
- observedGeneration
The most recent generation observed by the daemon set controller.
- updatedNumberScheduled
The total number of nodes that are running updated daemon pod
- Companion
- object
Value members
Concrete methods
Count 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.
Count 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.
If the field is not present, fails with com.coralogix.zio.k8s.client.UndefinedField.
Represents the latest available observations of a DaemonSet's current state.
Represents the latest available observations of a DaemonSet's current state.
If the field is not present, fails with com.coralogix.zio.k8s.client.UndefinedField.
The 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/
The 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/
This effect always succeeds, it is safe to use the field currentNumberScheduled directly.
The 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/
The 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/
This effect always succeeds, it is safe to use the field desiredNumberScheduled directly.
The 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)
The 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)
If the field is not present, fails with com.coralogix.zio.k8s.client.UndefinedField.
The 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/
The 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/
This effect always succeeds, it is safe to use the field numberMisscheduled directly.
The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.
The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.
This effect always succeeds, it is safe to use the field numberReady directly.
The most recent generation observed by the daemon set controller.
The most recent generation observed by the daemon set controller.
If the field is not present, fails with com.coralogix.zio.k8s.client.UndefinedField.
The total number of nodes that are running updated daemon pod
The total number of nodes that are running updated daemon pod
If the field is not present, fails with com.coralogix.zio.k8s.client.UndefinedField.