DaemonSet represents the configuration of a daemon set.
DaemonSet represents the configuration of a daemon set.
object
Property | Type | Description |
---|---|---|
|
|
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
|
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
|
|
DaemonSetSpec is the specification of a daemon set. |
|
|
DaemonSetStatus represents the current status of a daemon set. |
DaemonSetSpec is the specification of a daemon set.
object
selector
template
Property | Type | Description |
---|---|---|
|
|
The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready). |
|
|
The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10. |
|
A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template’s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors |
|
|
An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template’s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template |
|
|
|
DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet. |
DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.
object
Property | Type | Description |
---|---|---|
|
|
Spec to control the desired behavior of daemon set rolling update. |
|
|
Type of daemon set update. Can be "RollingUpdate" or "OnDelete". Default is RollingUpdate. Possible enum values:
- |
Spec to control the desired behavior of daemon set rolling update.
object
Property | Type | Description |
---|---|---|
|
The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption. This is beta field and enabled/disabled by DaemonSetUpdateSurge feature gate. |
|
|
The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update. |
DaemonSetStatus represents the current status of a daemon set.
object
currentNumberScheduled
numberMisscheduled
desiredNumberScheduled
numberReady
Property | Type | Description |
---|---|---|
|
|
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. |
|
|
Represents the latest available observations of a DaemonSet’s current state. |
|
|
DaemonSetCondition describes the state of a DaemonSet at a certain point. |
|
|
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 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 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 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 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. |
|
|
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) |
|
|
The most recent generation observed by the daemon set controller. |
|
|
The total number of nodes that are running updated daemon pod |
Represents the latest available observations of a DaemonSet’s current state.
array
DaemonSetCondition describes the state of a DaemonSet at a certain point.
object
type
status
Property | Type | Description |
---|---|---|
|
Last time the condition transitioned from one status to another. |
|
|
|
A human readable message indicating details about the transition. |
|
|
The reason for the condition’s last transition. |
|
|
Status of the condition, one of True, False, Unknown. |
|
|
Type of DaemonSet condition. |
The following API endpoints are available:
/apis/apps/v1/daemonsets
GET
: list or watch objects of kind DaemonSet
/apis/apps/v1/watch/daemonsets
GET
: watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.
/apis/apps/v1/namespaces/{namespace}/daemonsets
DELETE
: delete collection of DaemonSet
GET
: list or watch objects of kind DaemonSet
POST
: create a DaemonSet
/apis/apps/v1/watch/namespaces/{namespace}/daemonsets
GET
: watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.
/apis/apps/v1/namespaces/{namespace}/daemonsets/{name}
DELETE
: delete a DaemonSet
GET
: read the specified DaemonSet
PATCH
: partially update the specified DaemonSet
PUT
: replace the specified DaemonSet
/apis/apps/v1/watch/namespaces/{namespace}/daemonsets/{name}
GET
: watch changes to an object of kind DaemonSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the