Devops

I keep seeing the same debugging rabbit hole. A team adds CPU limits, latency gets weird, and the first question is: “Are pods getting killed?” Usually no. That’s memory behavior, not CPU behavior. CPU limits do not kill pods. They throttle them. That one distinction explains a lot of “everything looks fine but users are complaining” incidents. The Misunderstanding A lot of engineers assume this mapping: Memory limit exceeded → pod gets killed (OOMKill) ✅ CPU limit exceeded → pod gets killed ❌ The second one is the trap. The official Kubernetes documentation spells it out: ...

Last week I ran into a familiar mess, pods landing on nodes before the CNI plugin was actually ready. Kubelet marks the node as Ready, scheduler starts placing workloads, then everything sits in ContainerCreating because Calico is still coming up. I have worked around this with init containers and postStart tricks for way too long. I came across the Node Readiness Controller announcement on the Kubernetes blog. It is a new SIG project (v0.1.1), and it is basically what I wanted, custom readiness gates for nodes managed through a CRD. ...

🤖 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. ...

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. ...