If a new node is added to the cluster, what does a properly configured DaemonSet do?

If a new node is added to the cluster, what does a properly configured DaemonSet do?

• A. Launch a single pod on the new node
• B. Do nothing until manually updated
• C. Scale pods to multiple per node
• D. Delete itself

Answer: (A)

A DaemonSet is designed to run one instance of its pod on every node that matches its criteria, and it automatically brings up that pod on new nodes as they join the cluster. So when a new node appears, the DaemonSet controller creates a single pod on that node to maintain the one-per-node model. This automatic scheduling is what makes it useful for node-level agents like log collectors or monitoring daemons. If a node doesn’t match the DaemonSet’s selector or tolerations, it won’t run there, but for matching nodes it always provisions one pod on arrival. The other options don’t fit because DaemonSet does not wait for manual updates, it does not typically scale to multiple pods per node (one per node is the default), and it does not delete itself automatically.

A DaemonSet is designed to run one instance of its pod on every node that matches its criteria, and it automatically brings up that pod on new nodes as they join the cluster. So when a new node appears, the DaemonSet controller creates a single pod on that node to maintain the one-per-node model.

This automatic scheduling is what makes it useful for node-level agents like log collectors or monitoring daemons. If a node doesn’t match the DaemonSet’s selector or tolerations, it won’t run there, but for matching nodes it always provisions one pod on arrival.

The other options don’t fit because DaemonSet does not wait for manual updates, it does not typically scale to multiple pods per node (one per node is the default), and it does not delete itself automatically.