DevOps
Greetings, code warriors! Brace yourselves for a tech adventure. Today, we're exploring Loki, the log-aggregation maestro crafted to untangle your app's log mayhem. Fasten your seatbelts as we walk through setting up Loki in a K3s self-hosted cluster. It's the next chapter in my kube-prometheus-stack saga. Ready? Let's roll. Unlike
DevOps
Alright, buckle up – we're delving into the realm of Ingress controllers for Kubernetes, and our weapon of choice is none other than the robust ingress-nginx - community maintained. This powerhouse isn't just a preference; it's a strategic move. Let's dissect the intricacies, discover why it's a top pick, and then
DevOps
In the wild world of container orchestration, Kubernetes is the undisputed champ. Now, imagine your Kubernetes cluster as a bustling city—running apps, ensuring security, and doing all sorts of tech acrobatics. But, it's like working in the dark without proper monitoring. Sure, you can peek into the terminal, but
DevOps
Alright, let's dive into this scaling adventure. So, why bother scaling GitHub Actions runners? Well, let me drop some wisdom—it's all about the money $$. Those GitHub-hosted Linux runners don't come free ( 0.008$/minute ), and when your organization is juggling multiple teams, products, and staging environments, those costs start
DevOps
In the vast ocean of container orchestration, Kubernetes reigns supreme as the go-to platform for deploying and managing containerized applications at scale. But as your app's complexity grows, so does the challenge of managing deployments, configurations, and updates. Here's where Helm, the Kubernetes package manager, becomes your trusted first mate
DevOps
Been wanting to start a blog for a while, you know, a sort of documentation for the things I do but tend to forget. Never got around to it because it felt like an extra layer on top of what I'm already up to, plus, I'm not a fan of