DEV Community

Cover image for Understanding Kubernetes: part 32 – DaemonSet
Aurélie Vache
Aurélie Vache

Posted on

7 7

Understanding Kubernetes: part 32 – DaemonSet

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 :-).

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read more →

Top comments (2)

Collapse
 
aurelievache profile image
Aurélie Vache

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
 
omarkhatib profile image
Omar

Good job , amazing!!

Heroku

This site is built on Heroku

Join the ranks of developers at Salesforce, Airbase, DEV, and more who deploy their mission critical applications on Heroku. Sign up today and launch your first app!

Get Started