After 13.5 years as a loyal 1Password user, I'm hitting a breaking point with their browser extension. What used to be a seamless part of my daily workflow has become a constant source of friction.

After three years with the Mercedes EQB 350, I've come to a clear conclusion: Mercedes built an excellent car but failed to understand modern customer expectations.

It's been almost a year since I decided to set up Kubernetes on my home server, and I have to say, the experience has been a real rollercoaster. Let me share some of the highlights (and lowlights) with you.

On my personal microk8s cluster I unfortunately recently had a power failure affecting all nodes. I was using the default settings which create a file on /data/xxx.img. Unfortunately this file was missing from all my nodes.

I got a bus error when the postgres operator was running the bootstrap script. This happens when you have hugepages enabled (which is required to run mayastor). Many people claim you can simply disable huge_pages in postgres but I was not able to get this working. Instead, I simply just added a small allocation of hugepages to the postgres instance:

Over at Fenerum we are currently translating our software into multiple new languages, and while it worked fine for a while editing .po files by hand, it is now becoming a roadblock to getting things done.

I wanted a way to track the various websites I host in a privacy friendly way, so I decided on umami.is. Now, how do you set up umami on k8s?

After deciding to migrate to Kubernetes at Fenerum, I wanted to set up a homelab to play around in a safe environment and at the same time take the opportunity to start hosting various services myself.

A decade ago, I wrote about how we moved from Heroku to AWS at Plecto. Now, history has somewhat repeated itself at Fenerum, but this time with a different destination: Kubernetes.

Recently at Fenerum, we moved our test suite into Docker to improve consistency across environments. While this was the right architectural decision, it came with a performance hit - our test runtime increased from 50 minutes to 1 hour and 20 minutes.