Camel-K operator runs out of memory when deploying a new integration

Solution Verified - Updated -

Issue

When deploying a new integration using kamel run, the deployment fails, with an error message like the following in the operator log:

{"level":"info","ts":1647603178.6288633,"logger":"camel-k.maven.build","msg":"[INFO] skip non existing resourceDirectory /tmp/kit-c8q6o3pqajqk782qgur0-427541806/maven/src/test/resources"}
{"level":"info","ts":1647603239.24902,"logger":"camel-k.maven.build","msg":"[INFO] BUILD FAILURE"}
{"level":"info","ts":1647603239.2493243,"logger":"camel-k.maven.build","msg":"[INFO] ------------------------------------------------------------------------"}
{"level":"info","ts":1647603239.2519736,"logger":"camel-k.maven.build","msg":"[INFO] Total time:  01:14 min"}
------------------------------------------------------------------------"}
{"level":"info","ts":1647603239.3183706,"logger":"camel-k.maven.build","msg":"[ERROR] Java heap space -> [Help 1]"}

Environment

  • Red Hat Camel-K
    • 1.6.3

It is likely that other versions are affected.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content