How to pass additional native jvm args on kubernetes deployment?

[HerrDerb]

I would like to pass some additional native jvm args on deployment.
The current way to do so is

...
      containers:
        - args:
            - '-Xmn10m'
            - '-Xms1m'
            - '-Xmx30m'
          command:
            - ./application
          env:
...

While this does work, it overrides any arguments which are configured within the project over quarkus.jib.native-argument

I also tried to do something like quarkus.jib.native-arguments=$ADDITIONAL_NATIVE_ARGS with the idead that I could set a env variable for the container. With this, the container fails to start.

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "$ADDITIONAL_NATIVE_ARGS": executable file not found in $PATH: unknown.

What is a viable way in Quarkus and docker, kubernetes to pass additional native arguments at deploy time?

[quarkus-bot[bot]]

/cc @geoand (jib,kubernetes), @iocanel (kubernetes), @zakkak (native-image)

[geoand]

Just to clarify, you have built the native image container with quarkus-container-image-jib, you have deployed the application to Kubernetes and you are looking for a way to pass additional parameters to the launch command?

[HerrDerb]

Exactly. We build the container image containing the native application and push it to our registry. In our helm deployment we reference the image. Some of the native jvm properties, we can already set at build time. Some are depending on the specific deployment and can only be set at deploy time.

[geoand]

I can't think of anything off hand other than writing a custom launch script

[HerrDerb]

I see. I was hoping there might be a solution without having to build a custom base image. Thanks for you input 👍

[geoand]

🙏🏼

[HerrDerb]

Solved it with a custom native docker image

FROM quay.io/quarkus/quarkus-micro-image:2.0
COPY /runWithOptArgs.sh /work/runWithOptArgs.sh
ENTRYPOINT ["/bin/sh","/work/runWithOptArgs.sh"] 

whereas the entry point script looks like

echo "Build time native args: $@"
echo "Additional native jvm args: $ADDITIONAL_NATIVE_JVM_ARGS"
/work/application $@ $ADDITIONAL_NATIVE_JVM_ARGS