DaemonSet
A DaemonSet is a Kubernetes workload resource that ensures a Pod runs on each eligible node or selected nodes matching specified criteria.
Kubernetes in Action, Second Edition
A DaemonSet is a Kubernetes resource that ensures a pod instance runs on each eligible node or selected subset of nodes.
- How it is used
- Deploys node-level agents and daemons across eligible cluster nodes rather than distributing a fixed replica count.
- How deep it goes
- Works through manifests, placement checks, controller reconciliation, and update strategies; treats host access as Pod-template configuration.
- Examples
- Uses a sleeping-Pod manifest, GPU-labeled nodes, kubectl status checks, and a node agent reachable through a host port.
- What you can do after
- Operate/configure it with kubectl and manifests to inspect per-node Pods, select nodes, and choose an update strategy.
Read how Kubernetes in Action, Second Edition explains DaemonSet →
Logs and Telemetry
A DaemonSet is a Kubernetes workload controller that ensures a Pod runs on each eligible node or on a selected set of nodes.
- How it is used
- Deploys a node-level logging agent to collect container logs across Kubernetes nodes.
- How deep it goes
- Contrasts DaemonSet and sidecar operations, then details Fluent Operator configuration selectors and input performance limits.
- Examples
- Uses node-local Fluent Bit collection and a tail input for /var/log/containers/*.log routed to Elasticsearch.
- What you can do after
- Operate/configure it through Fluent Operator resources that define node monitoring and select logging inputs, filters, and outputs.
Acing the Certified Kubernetes Administrator Exam, Second Edition
A DaemonSet is a Kubernetes workload resource that ensures a pod runs on each eligible node.
- How it is used
- Ensures node-level pods remain present across a Kubernetes cluster.
- How deep it goes
- Explains one-pod-per-node scheduling, respawning, nodeName inspection, and kubectl verification, but not manifest construction.
- Examples
- Uses kube-proxy, CNI, kindnet, kubectl output, and kubelet systemd listings as operational examples.
- What you can do after
- Diagnose DaemonSet coverage with kubectl and distinguish missing DaemonSet pods from a stopped host-level kubelet.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains DaemonSet →
Related concepts
- kube-proxyused by · kube-proxy is a Kubernetes node component that maintains network rules forwarding service traffic to appropriate application pods.
- Kubernetes resourcekind of · A Kubernetes resource is a persistent API-managed object representing the desired or observed state of a workload, configuration, or other cluster entity.
- node selectorconfigured by · A node selector is a Kubernetes scheduling constraint that restricts a pod or workload to nodes having specified matching labels.
- podproduces · A Kubernetes Pod is the smallest deployable unit in Kubernetes, grouping one or more co-located containers that share networking and other resources.
- pod templatehas part · A pod template is a declarative specification embedded in a Kubernetes workload that defines the metadata, containers, and configuration of pods it creates.
- workloaduses · A workload is the amount, pattern, or set of work, tasks, or processing activity assigned to or carried out by a person, application, or computing system.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.