Kubernetes 101 - Component overview

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.
As mentioned in the previous article, on one side of Kubernetes, we get something called the control plane. This is the control system that can make decisions about the cluster. For example, ensuring enough pods are online at all times and routing tr...
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...

Before diving into the main setup and nitty-gritty stuff, let's take some time to explore the components that makeup Kubernetes.
This will help us better understand what we are talking about and how it links together.
The main thing to note (at least for me) is that there are things that make up the Kubernetes core and admin side and things we define for our actual application.
With this in mind, let's look at it in some more detail, starting with the Kubernetes provider high-level overview.

The above image demonstrates a Kubernetes cluster consisting of the following elements.
These nodes, in return, host something called Pods, which are the components of the application workload. The Control Plane manages all of this and ensures everything works as expected.
It's tough to explain each part in one extensive article, so I'll be splitting it into more detailed ones.
As you can tell many exciting things, we can go super broad or super niche. At the point of writing, I want to try and keep it high level so it will be easy for anyone with little to no experience to get to know Kubernetes.
Note: Keep in mind I'm also exploring while writing this, so do let me know if I got something misaligned.
It's important to note there are certain things we want Kubernetes to manage. This is all included in the Control Plane. As mentioned in the previous article, we don't want to be responsible for ensuring enough pods are running at a given time. And the Kubernetes API handles this perfectly for us.
On the other hand, we want our application to be dynamic and not bound to specifics for a particular server. Hence it's essential to run the node independently.
While this article is a bit short, we are in the early stages of explaining Kubernetes. I want to take the time to ask you for your input.
What are some concepts and things you want me to explore or think I should explain?
Let me know via Twitter/email or whichever way you find convenience. π
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter