How a 1 GiB Memory Limit Took Down My Entire k3s Cluster
18 Jun 2026
A single misconfigured resource limit triggered a cascade: OOMKill on the control-plane, load average of 90, 1.2M DNS queries per day, and kubelet reporting the wrong allocatable memory. Here's the full post-mortem.