#jvm

Kubernetes CrashLoopBackOff with OOMKilled exit code 137: Node heap set above the container limit

Our storefront BFF pods restarted every few hours with OOMKilled and exit code 137, then fell into CrashLoopBackOff during the holiday peak. A max-old-space-size inherited from the VM days was double the container memory limit. Sizing the heap to the limit and bounding a cache fixed it.