Why's there JDK inside the camel-k-kit-* images?

[bjethwan]

Why's there JDK inside the camel-k-kit-* images? And 384MB image for a simple route with basic log and timer components ?

This is using one of your samples

cd bipin_projects/camel-k-example-basic
kamel run Basic.java

dive bjethwan/camel-k-kit-cb2uqgpng1rc7386k9dg:6357

[astefanutti]

Thanks for raising it. JDK is required by the JOOR compiler, that compiles the Java routes at start time. It should be possible to use a JRE-only base image when using the other supported languages, and reduce the integration image size significantly.

[bjethwan]

@astefanutti I think you have a perfect case for cloud native buildpacks, paketo maybe.

[squakez]

We always need a JDK/JRE based container as at the end of the day we run a Camel application, so a buildpack style approach would be limited. Probably we can simply detect if an application has some java source (in which case we use the JDK), otherwise we can use a JRE image.

[github-actions[bot]]

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!

[squakez]

Closed in favour of #3743