Kubernetes DaemonSets guide

Now, how to create a DaemonSet. I already have a YAML file. DaemonSet is created using a kind called DaemonSet. Again, it has metadata, then a selector section, and it selects the same parts defined in the template labels. Finally, in the spec section, what you have is the container. It is the actual container that we want to run across all the nodes, all the pods.

There can be a variety of use cases, if you want the storage DaemonSet to be present on all the nodes, or you want to collect some log information from all the nodes. Again, if there is some specified script that runs on all the nodes, or whenever a new node joins, you want to run that particular script across the nodes or do node monitoring. All these use cases are pointing towards DaemonSet.

We will see a fairly simple example to calculate the memory from each node. You can see the image in the container section of the yaml file, and let's run this. First, we will use the kubectl create -f ds.yaml command. We can see that the DaemonSet is created. Now, use the command kubectl get ds. Again, you can see that two DaemonSets are there. You can also have a node selector in place if you want to specify it on specific nodes. Generally, it will run on all the nodes.

Now use the command kubectl get pods, and you can see both the pods created by DaemonSets are running. If I see the logs for a pod of the Daemon set by using the kubectl logs -f , it tells me how many MB is free and runs every five seconds. It is the same for the other one as well. We can also see additional information using the kubectl get ds -owide command. It will show you the selector and where the image is getting used. Also, if I use the kubectl get pods -owide command, we'll see that it's running on different nodes. This is because whenever we join a new node, it'll create a new pod of the same configuration and template we specified in the DaemonSet configuration. If we remove that particular node, it will go off.