In the last post of the series on my Kubernetes experiments, I described how to initialize the cluster. In this post, I will go into a bit more detail on what I did once I finally had a cluster set up. Tutorials Never having done anything with Kubernetes before, I started out with a couple of tutorials. The first one was this one. It uses Redis as an example deployment to demonstrate how to use ConfigMaps....
There are a lot of things we need to fix before we can get everyone on more climate friendly modes of travel, like trains. This was proven yet again by Deutsche Bahn. I like train journeys. They’re times where there is literally nothing to do but enjoy myself. There are no chores I can do, no work I have to do, nothing. Just free time. And in contrast to a couple of years ago, there is even decent Internet connectivity....
After setting up my lab environment in the previous article, I’ve now also set up the Kubernetes cluster itself, with kubeadm as the setup tool and Cilium as the CNI plugin for networking. Here, I will describe why I chose the tools I did, and how I initialized the cluster, as well as how to remove the cluster when necessary. Tools choice Before setting up a cluster, several choices need to be made....
So, as I mentioned in my last article, I want to give Kubernetes another try after HashiCorp’s recent license change. This also gives me a chance to put the lab back in Homelab, as it has mostly been a Homeprod environment - not much experimentation going on there, just slow, intentional incremental changes here and there. But my Homeprod env is not really suited for housing a Kubernetes cluster. It mostly consists of Raspberry Pis....
Basically my entire Homelab is build upon HashiCorp’s products. On August 10th, HashiCorp announced that they would switch all of their products to the BSL, the Business Source License, where they had been licensed under the Mozilla Public License before. From my (rather rudimentary!) understanding, the license basically says that all “non-production” use is perfectly fine. I’m pretty confident that that covers all of my own personal usage. But as it was pointed out to me today, that formulation also creates a lot of uncertainty for commercial entities of all kinds....