Answer
Before increasing memory, check the pod's logs for signs of an actual memory leak — simply giving it more memory only delays the same failure if there's a real leak driving the growth. To adjust workload sizing generally, the global.scale and global.cpuRatio parameters under the global section of ifscloud-values.yaml control how CPU/memory scale relative to production sizing (100 for production, around 50 often being enough for test) and the request-to-limit ratio, respectively — these are the supported way to resize workloads like the reporting pod. For a quick non-production test, directly editing the deployment's memory limit with kubectl edit deployment ifsapp-reporting-ren -n <namespace> works, but that edit gets overwritten the next time the installer runs, so it's a temporary diagnostic step, not a persistent fix.