Missing Kubernetes resource limits cause OOM kills

Containers without memory limits can consume unbounded resources, triggering OOM (out of memory) kills by the kernel. Missing CPU limits cause resource contention. Node.js 22's different V8 GC behavior changes memory usage patterns, causing unexpected OOM kills with old resource configurations.

Configure Kubernetes resources with requests (guaranteed allocation) and limits (maximum allowed). Set memory requests: 256Mi, limits: 512Mi; CPU requests: 250m, limits: 500m. Tune based on actual usage. Monitor memory patterns after Node.js version upgrades as GC behavior changes. Adjust limits to accommodate new memory patterns.