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).
I start this serie of Sketchnotes about Kubernetes with one kind of resource: Pods.
If you are interested, I published an entire illustrated book about Kubernetes, available in paperback on Amazon and in digital version on GumRoad: "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 :-).
Top comments (25)
Hi @aurelievache
Thank you for sharing.
I started working on kubernetes recently, and I'm using GKE in autopilot mode.
I noticed that when I tried to use the pods (several hundred) (using jobs) to run some algorithms that require several minutes (>15 min), K8S was selecting pods randomly and kill them.
To solve the issue, I was able to change the data chunk size to make the each tasks faster (less than 2 min).
Now, I'm wandering: Are the PODS, and kubernets in general, a good tool for running long-time processing algorithms ?
Thank you again.
Kind regards.
Hi and thank Mohamed
Pods are mortal by design, ther are not supposed to live forever :-)
For your need, you can use Jobs, as you already used it.
Have you defined a good activeDeadlineSeconds parameter in jobs spec?
"The activeDeadlineSeconds applies to the duration of the job, no matter how many Pods are created. Once a Job reaches activeDeadlineSeconds, all of its running Pods are terminated and the Job status will become type: Failed with reason: DeadlineExceeded."
So you can increate it for your needs for example, and also run several pods in parallel in order to parallelize your job
Thank you @aurelievache
Does this mean that I should never deploy a queuing system like rabbitmq as a pod?
In my case, the queuing system is very active in the application. All other pods rely on it. if the queuing system pod fails, I'll need to waste time before I can resume the process.
Salut, Aurélie! Il est toujours utile d'expliquer les concepts fondamentaux. Une bonne documentation permet d'éviter les nuits blanches.) Je connais Docker. Et je délègue la configuration cloud à DevOps.
Pourrais-tu m'aider s'il te plaît. J'ai besoin d'un examen de mon #showdev sur dev.to. Merci)
Bonjour Chloé,
Je n'ai pas trop compris.
De quelle aide a tu besoin ? 😉
Aurélie, j'aime le développement de produits. Y a-t-il des idées intéressantes sur les kubernetes? Je veux dire que cela pourrait être cool pour les autres, et c'est facile à faire.
Je suis désolé. On dirait qu'il est considéré comme du spam.
Yes, I imagine pods like pokeballs which can contenate one or several containers 🙂.
Happy you like the kube sketchnotes serie.
The difference between Dev and production can be the scaling auto with hpa, but also the multi region, the security, the network policies... Many things to talk if you are interested🙂
I really like the way K8s explained via sketch notes. Great job. May I know if the sketch are drew from hand or any software is used? If software may I know the name?
Thanks
thanks :)
sketchnotes are drawn by hand with a samsung pencil :)
Wow! That's Amazing. Thanks for the update.
Nice
This is brilliantly drawn, Aurelie! Could you please publish a similar series for Webservers (Nginx, HAProxy, Traefik etc..)
Thanks 😊
I will publish a serie about Istio, soon, and then maybe Traefik, I am thinking of futures series 🙂
I note for HaProxy and Nginx too.
I've recently started working with Istio so I'm looking forward to your sketchnotes on it 😄
This is awesome! Special request for PVCs (including storage class, volume, volume mount) and for Ingress.
Thanks for your kind words :-).
I've created 10 sketchnotes yet, I will publish them shortly and started yesterday a sketch about storageclass, pv and pvc :-).
I note for Ingress :-).
Thanks for this amazing work and making it available.
Très cool Aurelie. La série est excellente. Merci.
Merci 🙂
J'espère que la suite te plairas autant 😉
I am amused by your runnab "to the power L" e. 😊😊😊
Some comments may only be visible to logged-in visitors. Sign in to view all comments.