What are the typical application scenarios of DaemonSet

This article shows you what are the typical application scenarios of DaemonSet, which are concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

The replica Pod of the Deployment deployment is distributed across the Node, and each Node may run several copies. The difference with DaemonSet is that at most one copy can be run on each Node.

Typical application scenarios of DaemonSet are:

Run a storage Daemon, such as glusterd or ceph, on each node of the cluster.

Run log collection Daemon, such as flunentd or logstash, on each node.

Run a monitoring Daemon, such as Prometheus Node Exporter or collectd, on each node.

In fact, Kubernetes itself is using DaemonSet to run system components. Execute the following command:

Kubectl get daemonset-namespace=kube-system

DaemonSet kube-flannel-ds and kube-proxy are responsible for running flannel and kube-proxy components on each node, respectively.

Because flannel and kube-proxy are system components, you need to specify namespace kube-system through-- namespace=kube-system on the command line. If not specified, only the resources in the default namespace default are returned.

What are the typical application scenarios of DaemonSet? have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.