New Service OOMed 2 Hours After Launch: Replacing Manual Approval with a 7-Dimension Production Readiness Gate
Overview 1:47 AM. Phone buzzed. Alert channel exploded. A newly launched recommendation service at a ride-hailing project went OOMKilled on all 3 Pods less than 2 hours after launch. Memory spiked from 800MB to the 2GB limit, the kernel killed the process, Kubernetes restarted the Pod, and it got killed again. Loop. Users were routed to the fallback path. P99 latency shot from 80ms to 2000ms. The postmortem found the root cause....