Posts

🤖 A New Era of Creation We’re living through something extraordinary. AI isn’t just automating tasks, it’s amplifying imagination. As someone who’s spent years deep in the world of infrastructure, automation, systems, and DevOps, I find myself more excited than ever. Not because AI replaces what we know, but because it lets us build upon it faster than ever before. 💡 Ideas Used to Be Worthless Without Execution For most of IT history, ideas were… expensive. You could have a vision, a product concept, a technical improvement, but without: ...

🧠 The Problem As a DevOps engineer with a Linux-first background, you eventually face this: You’re given a company-issued laptop or you’re working for a client, and their policies require you to use Windows. Fair enough. Modern Windows is solid. With WSL2, you can run a real Linux kernel, your dotfiles work, and tools like Docker, Git, and SSH behave mostly as expected. But then… small things get in the way. Like window switching. ...

Detecting Kubernetes Nodes Running Only DaemonSet Pods, A Deep Dive A real-world story about PromQL struggles, Helm templating, alert design, and operational savings by Dedico Servers. Executive Summary At Dedico Servers, we specialize in building efficient, cost-optimized Kubernetes clusters. In this article, we engineer a Prometheus-based alert to detect nodes running only DaemonSet pods, an operational and financial risk. By tackling this hidden inefficiency, we help our clients save thousands of dollars annually while improving the resilience of their clusters. ...

Managing Kubernetes applications with ArgoCD is already a game-changer, but what if you need to deploy the same app across 10 clusters, or generate dynamic app configs based on Git branches or Helm values? That’s where ApplicationSets step in. 🚀 What is an ApplicationSet? An ApplicationSet is a Kubernetes custom resource that tells ArgoCD how to automatically generate multiple Application resources from a template. It’s like templating your ArgoCD apps, letting you define how they should be generated and where they should go. ...

What is DevOps? DevOps is not a tool, not a job title, and not a product you can buy. It’s a culture and set of practices that breaks down the walls between software development and operations. In traditional organizations, developers write code, throw it over the wall to operations, and hope it works. Operations dreads every change because change means instability. Everyone protects their own silo. DevOps transforms this model: the team is collectively responsible for the code from idea to production. ...

Kubernetes Is Not the Answer to Every Problem I say this as someone who spends a significant part of their work building and operating Kubernetes clusters. Kubernetes is a fantastic tool — but it’s not for everything, and introducing it at the wrong time can cause more problems than it solves. When to Use Kubernetes Many microservices (10+) that scale independently Variable load — autoscaling handles capacity automatically Multiple teams and environments — namespaces and RBAC provide clean separation High availability requirements (99.9%+ uptime) — self-healing, health checks, rolling updates Multi-cloud or hybrid strategy — Kubernetes abstracts the provider When NOT to Use Kubernetes One or two simple applications — use a VPS, Docker Compose, or managed PaaS instead Small team with no K8s experience — the learning curve takes months No CI/CD pipeline yet — build that first; Kubernetes builds on top of it Cost-sensitive project — minimum production EKS cluster costs $250-800/month Legacy stateful apps not designed for containers — significant refactoring needed Decision Framework Ask yourself: Do you have 5+ independently deployable services? Variable load needing autoscaling? K8s expertise on the team? Budget for minimum K8s costs? Containerizable services? ...

Why Do You Need a CI/CD Pipeline? If your deployment process involves someone SSH-ing into a server and running commands manually — every deployment is a risk. Forgotten steps, drifting configurations, human errors. A CI/CD pipeline automates the entire flow from code to production. Every deployment becomes identical, repeatable, and safe. The Five Layers of a CI/CD Pipeline 1. Source Control Git with a branching strategy (trunk-based development recommended), PR reviews, and protected main branch. ...

Tailscale makes it incredibly easy to build secure, private networks between devices, and it works brilliantly inside Kubernetes too. In this guide, we’ll run a Kubernetes pod as a Tailscale client, routing its egress traffic through a Tailscale exit node. ✅ Use case: You want a pod to access the internet through a specific IP/location (e.g., a static home server) while maintaining full mesh connectivity over Tailscale. 🧱 Requirements A Kubernetes cluster (k3s, k8s, or managed service) A working Tailscale account An exit node already configured and enabled in Tailscale Linux container support (Debian-based preferred for Tailscale) 🐳 Step 1: Create a Tailscale-enabled Pod Here’s a basic example using an init container to authenticate and set up Tailscale. ...