DaemonSets for per-node workloads in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a DaemonSet in Kubernetes?

A DaemonSet ensures that a copy of a specific pod runs on all or some nodes in a Kubernetes cluster. It is used for running per-node workloads like monitoring or logging agents.

intermediate

How does a DaemonSet differ from a Deployment in Kubernetes?

A Deployment manages pods that can run anywhere in the cluster and scales by number of replicas, while a DaemonSet runs exactly one pod per selected node, ensuring per-node coverage.

beginner

Which Kubernetes resource would you use to run a logging agent on every node?

You would use a DaemonSet to run a logging agent on every node, because it guarantees one pod per node.

intermediate

What happens to DaemonSet pods when a new node is added to the cluster?

When a new node joins the cluster, the DaemonSet automatically creates a pod on that node to maintain one pod per node.

intermediate

Can you limit a DaemonSet to run pods only on specific nodes?

Yes, by using node selectors or node affinity rules in the DaemonSet specification, you can restrict pods to run only on certain nodes.

What is the primary purpose of a DaemonSet in Kubernetes?

A Manage persistent storage

B Scale pods based on load

C Control network policies

D Run one pod on every node

A DaemonSet runs exactly one pod on each node to handle per-node tasks.

If you add a new node to your cluster, what does the DaemonSet do?

A Creates a pod on the new node

B Scales pods to zero

C Deletes pods on other nodes

D Does nothing automatically

DaemonSet automatically creates a pod on the new node to maintain coverage.

How can you restrict a DaemonSet to run pods only on Linux nodes?

A Use nodeSelector with OS label

B Use a Deployment instead

C Set pod replicas to zero

D Use a ConfigMap

Using nodeSelector with the OS label limits pods to Linux nodes.

Which workload is best suited for a DaemonSet?

A Database cluster

B Node monitoring agent

C Web application with variable scaling

D Batch job

Node monitoring agents need to run on every node, so DaemonSet is ideal.

What happens if a node is removed from the cluster?

A Pods remain running on the removed node

B Pods move to other nodes automatically

C DaemonSet pods on that node are deleted

D DaemonSet creates extra pods on remaining nodes

When a node is removed, its DaemonSet pods are deleted with it.

Explain what a DaemonSet is and why it is useful in Kubernetes.

Think about workloads that need to run everywhere in the cluster.

Describe how you can control which nodes a DaemonSet runs pods on.

Consider how Kubernetes matches pods to nodes.