DEV Community

loading...
Cover image for Understanding Kubernetes: part 32 – DaemonSet

Understanding Kubernetes: part 32 – DaemonSet

Aurélie Vache
Cloud Developer - Google Developer Expert on Cloud - CKAD - Speaker - Sketchnoter - Technical writer - Conferences organizer - "Duchess France" women in tech association Leader - Mentor
・1 min read

Understanding Kubernetes can be difficult or time-consuming. In order to spread knowledges about Cloud technologies I started to create sketchnotes about Kubernetes. I think it could be a good way, more visual, to explain Kubernetes (and others technologies).

We continue the serie of Kubernetes Sketchnotes with a focus on DaemonSet.

Alt Text
Alt Text
Alt Text
Alt Text

If you are interested, I published all the sketchnotes on Kubernetes (and new ones!) to make a "book" of 120 pages: "Understanding Kubernetes in a visual way".

As usual, if you like theses sketchnotes, you can follow me, and tell me what do you think. I will publish others sketchs shortly :-).

Discussion (4)

Collapse
pjotre86 profile image
pjotre86

I kind of get it. Could you maybe illustrate it with an easy example where daemon sets make sense? That's not really clear to me yet...

Collapse
aurelievache profile image
Aurélie Vache Author

Daemonset are useful for example if you want to deploy logs collector, node exporters, logs rotate...

If you need to have your application deployed on each node in the cluster, you need to deploy your app in a DaemonSet.

In the real world, you will deploy a lot of deployments, and jobs or CronJobs.

Daemonset, statefulset it's only for certain specific cases.

Collapse
pjotre86 profile image
pjotre86

I see. Thanks a lot! And kudos for all the illustrations so far!

Collapse
elkhatibomar profile image
Omar

Good job , amazing!!

Forem Open with the Forem app