liveBook · Manning

DaemonSet controller

As explained in Kubernetes in Action, Second Edition

A DaemonSet controller is the Kubernetes controller that reconciles a DaemonSet by creating and managing its pods across eligible nodes.

A DaemonSet controller reconciles a DaemonSet by creating and managing its pods across eligible nodes. It uses the DaemonSet’s selector and pod template, then reports node-based progress in status. section 17.1.2

Watching controller results

For a demo DaemonSet, kubectl describe shows the selector, pod template, scheduled-node counts, pod states, and related events. kubectl get ds -o yaml exposes fields such as desiredNumberScheduled, numberReady, numberAvailable, and updatedNumberScheduled.

Interpret controller status as counts of nodes rather than simply counts of pods:

  • During a pod-template update, old and new pods can overlap while the new pod becomes available. section 17.1.2

How Kubernetes in Action, Second Edition covers it

How deep it goes
Explains selectors, templates, node-based status, and update overlap, but does not detail controller implementation internals.
Examples
Uses a demo DaemonSet manifest, kubectl inspection commands, node listings, and status-field examples.
What you can do after
Diagnose DaemonSet coverage and rollout state with kubectl status, describe, YAML, and pod queries.
How it connects
Connects DaemonSets with pods, pod templates, node selectors, object status, and reconciliation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.