Kubernetes 101 - Node component

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
I wanted to explore Pods in more detail as they are quite an essential aspect of the Kubernetes ecosystem. You can take the name Pod as the literal sense of "pod of whales" or "pea pod," meaning it's one single element in a group of elements. In the ...
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

We'll check out the node component in more detail for this article.
The node component is a component that runs on every node, and it's responsible for maintaining running pods and providing the Kubernetes runtime environment.
It closely connects with the Kubernetes API and receives and sends data from its node.
Each node runs two main components a kubelet and a container runtime. Let's take a look at what each one does.
The kubelet is responsible for establishing and acting on the communication between the Control Plane and the node.
The container runtime is in charge of pulling the relevant image from the image registry, unpacking them, and running them on the node. It can run multiple container runtimes, including Docker, CRI, CRI-O, and Containerd.
Besides the two main components, we also get the kube-proxy which runs on each node. It's responsible for maintaining network rules on each node. It makes sure the communication between nodes and pods is as expected.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter