-
My self-hosted AI journey Part 2: Using Ollama as your coding assistant
One of the big use-cases for AI for developers today is coding-assistants. It basically serves as your assistant for useful suggestions, a sparring-partner, and occationally you can hand off larger tasks to it while you are taking a lunch break. Hiring human assistants means you can have them sign work contracts and confidentiality agreements –…
-
Playing with AIs at home – beginning the journey
After having upgraded my home server, I found myself with an abundance of both CPU power and memory, both of which are meant to be used. After having given my other down-scaled components the memory and CPU they truly need, I decided to see what my new hardware could be used for. One of the…
-
A hardware upgrade!
In short: In essence, I wanted to play with fun functionality instead of battling defects and too little resources. So, I went on a shopping hunt. And I found The Beelink GTI14 Ulta 9. I spec’ed it high, with 2*1TB m.2 SSD (I somewhat regret not going for lower (it was the max), and rather…
-
Kubernetes DR Part 4 – Addendum: How I solved the complete DR activation
My DR activation strategy is about injecting state into the ArgoCD applications. One state I am already injecting globally is the cluster I am on, via the in-cluster secret, and based on that I set the env variable to either prod or DR. This is done through the cluster generator. I basically set the cluster…
-
Kubernetes DR Part 3 – migrating the workload applications
In my previous blog post, I got as far as having an identical gitea in DR, with the same repositories that exists on-prem. They will, of course, not stay identical for very long without finding a way to keep them in sync. Before starting to migrate applications to applicationsets and create them in DR, I…
-
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…