Progressive Hints

Hint 1 (after 5 min)

Look at the memory limit on the pod and compare it to the Redis memory usage metric. Pay attention to the units. 64Mi is 67,108,864 bytes. The Redis metric shows usage approaching that number.

Hint 2 (after 10 min)

The Helm values set maxmemory-policy noeviction — Redis will never evict keys, so memory can only grow. Combine that with the 64Mi container limit: once Redis memory usage reaches the container limit, the kernel OOM-kills the process (exit code 137).

Hint 3 (after 15 min)

This is an e-commerce session store (namespace ecommerce, label session-cache, 48K keys, 312 connected clients from a web app). Redis is configured as a pure in-memory cache with no persistence — but the noeviction policy means it will refuse writes rather than evicting old sessions, causing memory to grow until the container is OOM-killed. The fix involves either raising the memory limit or setting a proper eviction policy. The "Can't save in background" log is a red herring — persistence is disabled, so that background save attempt is harmless.