The JVM xmx parameter set on KOGITO-306 seems to not be enough to avoid OOMKilled pods.
This is because the JVM seems to occupy all the memory available instead of a portion of it. Ideally, we should reserve ~20% of memory for the pod to run.
- relates to
-
KOGITO-306 Limiting GraalVM memory usage on Quarkus s2i images builds
- Resolved
-
KOGITO-416 Limiting GraalVM memory usage relying on container cgroups
- Resolved