-
Kubernetes DR Part 2: Building infrastructure applicationsets for my clusters.
Having installed a new cluster including getting ArgoCD to run, it’s time to think about deploying some applications. From earlier, I have simple applications that are very much tailored to running on my already existing cluster: Setting up a DR cluster, I need to make my DR cluster creating similar applications with some properties changed.…
-
Setting up a second DR cluster part 1 – bootstrap script.
My primary cluster was installed manually. While I have retroactively created some scripts and put it in my bootstrap repository, it had never been tested end-to-end. Creating a DR cluster (still only one node) was a perfect opportunity to test that. The goal of the bootstrap repo/script is to have scripted procedure to install the…
-
A real incident: Longhorn recovery
Running Longhorn with multiple replicas over long distance isn’t exactly recommended. Longhorn works best on a local network, where network in general is stable and you don’t lose connectivity between the nodes so often. I ignored this for a while, because I wanted to test a dual-node longhorn setup, but in the end I paid…
-
Longhorn – a Kubernetes-native filesystem
The other day, I took a look at Longhorn again. I briefly looked at it earlier, as a way to get volumes that are writeable from more than one node. I tossed it away then, because I mistook it for nothing more than a glorified NFS server. I was quite wrong. At the time of…
-
RIP Bitnami…and some reflections on convencience vs simplicity
Bitnami, which was once regard as a readily available and reliable source of containers and helm chart, was recently bought by Broadcom. Broadcom has made the decision to host their containers and Helm chart behind a subscription paywall, and no longer provide a helm chart repository or their full docker image catalog for free. While…
-
The road to enterprise at home: Crafting a proper DR strategy.
In my previous post I did a proof of concept of recreating my infrastructure at a secondary node. While it worked, it was highly manual, and it took some downtime until I actually got around to do it. A proper DR solution, however, should be pre-made, ready to be enacted. It can still be partly…
-
The road to enterprise at home: A DR-test!
I’ve had some issues with my kubernetes-node, basically a few random crashes. A bit inconvenient as it’s summer-time. As I am writing this, I am at our cabin and the kubernetes-node is down. But wait a minute? Doesn’t the blog run on kubernetes? Yes, it does. But I do have backup. A while back, I…
-
Kubernetes configuration as code – Gitea and ArgoCD
Until a couple of days ago, all my Kubernetes config has lived simply as yaml-file residing in a tree in my home directory. While I had all the configuration, and knew where to find it if I needed to change it, it became a bit difficult to keep overview over time, and especially was it…
-
Resource Management in Kubernetes
If your cluster is small, it might be fine to just trust that everything is fine, behaving nicely, and gets the resources they need. Having experienced a bit of performance issues, greedy components eating much resources, and even affecting the stability of the cluster itself, I found that it was time to dive into the…
-
Kubernetes monitoring – we love metrics!
Kubernetes is often self-healing. Containers will restart, operators will continuously try to apply the desired state, but there might be things you want to know about, and things that can’t be solved automatically. You probably also do care about things like the performance over time, and bottlenecks in your system, and maybe you wants some…