Right now the Kogito native S2I build of OpenShift takes a significant amount of memory.
Recent experiments showed that onboarding S2I build [1] can require more than 5GB of memory. Considering that there are no build pod limits defined this situation can lead to Out Of Memory issues on OpenShift node.
Build pods should correctly handle their requirements or significantly reduce their resource usage.
[1] https://github.com/kiegroup/kogito-examples/tree/master/onboarding-example/onboarding
- is related to
-
KOGITO-305 Add an option to add a maven mirror URL through CLI/CR
-
- Resolved
-
-
KOGITO-306 Limiting GraalVM memory usage on Quarkus s2i images builds
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
