camel-k
camel-k copied to clipboard
Configure memory resource requests on builder pods
If you have set a memory limit range on a namespace, such as
davsclaus:/workspace/camel-k/examples (master)/$ k describe LimitRange mem-limit-range
Name: mem-limit-range
Namespace: default
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container memory - - 25Mi 100Mi -
And then for example run a kamel integration where a new build is needed, then the builder pod runs out of memory.
│Status: │
│ Base Image: fabric8/s2i-java:3.0-java8 │
│ Duration: 2.142086252s │
│ Error: failure while determining classpath: signal: killed │
│ Failure: │
│ Reason: failure while determining classpath: signal: killed │
│ Recovery: │
│ Attempt: 5 │
│ Attempt Max: 5 │
│ Attempt Time: 2019-11-25T17:09:23Z │
│ Time: 2019-11-25T17:07:06Z │
│ Image: fabric8/s2i-java:3.0-java8 │
│ Phase: Error │
│ Started At: 2019-11-25T17:09:25Z │
│Events: <none>
So we should set some reasonable memory requests for the builder pods so they wont run out of memory, as they are Java Maven builds then they take up a good portion of memory.
This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!
It seems to be still relevant.
Done in Camel K version 2: https://camel.apache.org/camel-k/next/traits/builder.html