How a Request Actually Reaches Your Pod
Every hop from the browser to the process inside the container, with the mechanism behind each one. Load balancer, node, kube-proxy, iptables, veth pair, network namespace, socket. Nothing skipped.
Read postThe DevOpsBeast Blog
Field notes on Kubernetes, GPUs, Linux, and the rest of the production stack, from engineers who run real infrastructure.
Every hop from the browser to the process inside the container, with the mechanism behind each one. Load balancer, node, kube-proxy, iptables, veth pair, network namespace, socket. Nothing skipped.
Read postEvery Service create rewrites your entire iptables chain. At small scale you never notice. At 5,000 Services kube-proxy is at 100% CPU, Service updates take 30 seconds, and your latency p99 is in the seconds. Here is the cliff and how to fall off it.
Read postndots:5 is the silent latency killer in Kubernetes. Every external hostname resolution generates four wasted queries before the right one. Here is why, and how to fix it.
Read post