Kubernetes

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

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