kubernetes

In my professional life I use terraform, kubernetes, various cloud providers… Why did I choose k8s as a solution for my self-hosted server overhaul? Was it a good idea? Reasoning As a DevOps professional, I always strive to learn new things. However, in projects, there isn’t always space to experiment with new concepts. Small changes can break many things, and some chosen architectures are already deeply integrated with other components. When I go with smaller scale and personal server I still have a lot of things that I cant test and learn from....

After deploying k3s on one of my servers (which I will post about later) I searched for a solution to manage the components deployed on it. My first thought was to use terraform, but it has several drawbacks when it comes to k8s and helm support. Additionally it needs managing unnecessary state files managing even for that simple task. While it may be worth sticking to one tool if everything is in it, this was not the case for me this time....

For years I’ve been using my private git server. I started with Gogs, then moved to Gitea, and soon I’m updating to Forgejo. Initially, I only used it to store some non-public repositories (as private repos on GitHub were not free back then). However, for quite some time now, I’ve been using it to store the configuration of my personal servers. As a result, I needed a CI/CD system, and that’s where Woodpecker comes in....