We support JVM configuration in Operator. This was added as BAPL-1507. I tried to put into KieApp.yaml this:

 objects:
    console:
      env:
        - name: GC_MAX_METASPACE_SIZE
          value: '1300'
        - name: JAVA_MAX_MEM_RATIO
          value: '40'
      jvm:
        gcMaxMetaspaceSize: 1000
        javaMaxMemRatio: 80
      resources:
        limits:
          memory: 3Gi

So now we have two ways, how to set JVM properties for deployments, if we combined both of them, then are used env values. In pod log is displayed this configuration: -Xmx1229m -XX:MaxMetaspaceSize=1300m

The env vars configuration wins over the JVM vars, and duplicate parameters are not added to the java command. This is correct behavior.

Goal of this jira:
Add tests to Operator so we can be sure it still works same in future and that we did not break it by any new changes