Write about the usage scenarios of DaemonSet and yaml cases

DaemonSet is a controller object in Kubernetes that is used to run a copy of a Pod on each node in the cluster. It is suitable for tasks that require one instance to run on each node, such as log collection, monitoring agents, etc. The following are some typical scenarios for using DaemonSet:

1. Log collection: If you need to collect container logs on each node and transfer them to a centralized logging system, you can use DaemonSet to deploy a log collection agent, such as Fluentd or Filebeat, on each node.

2. Monitoring agent: used to monitor the resource usage, performance indicators, etc. of each node in the cluster. Node-level monitoring data can be collected by running a monitoring agent, such as Prometheus Node Exporter, on each node.

3. Edge Computing: In edge computing scenarios, specific applications or agents need to be run on each edge node. DaemonSet can ensure that there is a copy running on each edge node to provide edge computing services.

Here is a simple YAML example of DaemonSet:

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: my-daemonset
spec:
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
        - name: my-container
          image: my-image
          ports:
            - containerPort: 8080

In this example, a my-daemonsetDaemonSet named DaemonSet is defined. It uses my-appa tag selector named to select Pods to manage. Each Pod has a my-containercontainer named , uses my-imagean image, and exposes port 8080.

This example shows how to use a DaemonSet to run a copy of a Pod on each node to provide a specific service or task.

Please note that the use of DaemonSet requires appropriate configuration and adjustment according to actual needs.

Hope this example helps you! If you have any further questions, please feel free to ask.