Explain how DaemonSets are used in Kubernetes and provide an example of a common use case.

DaemonSets in Kubernetes are used to ensure that a copy of a Pod runs on all (or some) nodes in a cluster. They are typically used to deploy system-level services or agents that need to be present on every node for monitoring, logging, or other infrastructure-related tasks. Unlike Deployments or ReplicaSets, which manage a specific number of replicas across the cluster, DaemonSets guarantee a Pod instance on each selected node. When a new node is added to the cluster, the DaemonSet automatically deploys a Pod on that node. Similarly, when a node is removed from the cluster, the DaemonSet automatically removes the Pod from that node. How DaemonSets work: DaemonSets use a node selector to determine which nodes should run the DaemonSet Pods. The node selector is a set of labels that the DaemonSet uses to match nodes. By default, if no node selector is specified, the DaemonSet will schedule a Pod on all nodes in the cluster. The DaemonSet controller is responsible for ensuring that the desired number of Pods are running on the selected nodes. It monitors the nodes in the cluster and creates or deletes Pods as needed to maintain the desired state. Common use cases for DaemonSets: Logging agents: DaemonSets are commonly used to deploy logging agents, such as Fluentd or Elasticsearch, to collect logs from all nodes in the cluster. Monitoring agents: DaemonSets are also used to deploy monitoring agents, such as Prometheus Node Exporter or Datadog Agent, to collect metrics from all nodes in the cluster. Network plugins: DaemonSets can be used to deploy network plugins, such as Calico or Weave Net, to provide networking functionality to the cluster. Storage agents: DaemonSets can be....