Answer
Memory/heap-related tuning for an individual pod is generally exposed through the installation values file rather than being fixed per pod — if a specific pod repeatedly hits its memory ceiling, investigate whether its resource limits or JVM heap settings can be tuned there, and capture a heap dump for that pod to understand what's actually consuming the memory before assuming a blanket resource increase is the fix.