-
Enhancement
-
Resolution: Done
-
Minor
-
0.5.0
-
None
Today we're relying on LIMIT_MEMORY environment variable to set the JVM max memory usage for native builds.
This seems to not be the better way of achieving this since we're relying on environment variables set by the operator. Ideally, would be better to not rely on the operator and limiting the way each other is interconnected.
This article can be a good source of information:
https://medium.com/@asishrs/docker-limit-resource-utilization-using-cgroup-parent-72a646651f9d
- blocks
-
KOGITO-417 Remove LIMIT_MEMORY and LIMIT_CPU environment variable from s2i BuildConfig
- Closed
- is related to
-
KOGITO-419 When building native applications, builder pods get OOMKilled
- Resolved
- relates to
-
KOGITO-306 Limiting GraalVM memory usage on Quarkus s2i images builds
- Resolved