Reshapr control plane and proxy are written in Java using Quarkus, and their container images thus use a JVM. JVM is great for performance and throughput on long runs, but not so great regarding the size of container images, the startup time, and memory consumption. So, depending on the use case, it could be a game-changer to have GraalVM native container images that can be pulled and start super-quickly.

Typically, when using the reshapr proxy as a sidecar container as we proposed to do so in #123, it makes a lot of sense to use a lightweight flavour of the reshapr-proxy container images.