Kubernetes 101 - Containers

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.
A big part of Kubernetes is the networking capabilities, we get the option to internally route traffic to neighbouring pods, split workloads on multiple nodes and even open up networking to the outside world. Let's take a closer look at some of the e...
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...

For this article we'll be looking a bit more in detail into containers. Containers are ready to run software packages, meaning they include everything:
Once something is converted into a container the code cannot change, if you need to update any of the above mentioned elements you'll need to create a new image version.
The benefit of these images containing everything out of the box is that the can easily run on different OS environments and clouds.
As for the container images it references a bundles application that you can run on a given pod.
So where do these images live?
By default Kubernetes will look in the Docker registry for your images based on it's name. However it's possible to use other registries as well as private hosted ones.
We won't go into too much detail around this for now.
The main thing here is to know that at some point we'll have to convert our code into a image and push it somewhere.
Hooks are not a new concept, but something worth mentioning. Our containers come with some hooks exposed, there are two exposed ones:
PostStart: Executed immediately after creation of the container.PreStop: Called before the container is terminated due to unhealthiness of controller decided to kill it off. It's important to note the container will always be killed, it won't wait for some calls to happen in this hook.For our beginning exploration of Kubernetes we won't use these hooks just yet, so let's dive into them at a later stage again.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter