jkube.container-image.platforms=linux/amd64,linux/arm64 seems to takes no effect

[tdiesler]

Describe the bug

Property -Djkube.container-image.platforms=linux/amd64,linux/arm64 seems to take no effect. Not in the pom, nor on the cmd line.

Having this in the pom works ...

    <from>eclipse-temurin:17</from>
    <platforms>
        <platform>linux/amd64</platform>
        <platform>linux/arm64</platform>
    </platforms>

Eclipse JKube version

1.18.0

Component

Kubernetes Maven Plugin

Apache Maven version

None

Gradle version

None

Steps to reproduce

Build a mvn project using -Djkube.container-image.platforms=linux/amd64,linux/arm64

Expected behavior

Output similar to

[INFO] k8s: .../git/camel-cloud/camel-main/timer-log/target/docker/examples/timer-log/1.0.0/tmp/jib-image.linux-amd64.tar successfully built
[INFO] k8s:  .../git/camel-cloud/camel-main/timer-log/target/docker/examples/timer-log/1.0.0/tmp/jib-image.linux-arm64.tar successfully built

Runtime

Kubernetes (vanilla)

Kubernetes API Server version

1.25.3

Environment

macOS

Eclipse JKube Logs

Sample Reproducer Project

No response

Additional context

No response

[rohanKanojia]

@tdiesler : Are you using the jib build strategy?

[gansheer]

If you don't mind @tdiesler , I'll add some context. We are using jkube in one of our tooling to build container images. We provide the possibility to use docker, podman and jib.

So we were setting by default the following configuration in the pom.xml expecting it to be ignored in case of a non-jib build:

<createImageOptions>
    <platform>linux/amd64</platform>
    <platform>linux/arm64</platform>
</createImageOptions>

But we realised in the case of a docker build having this configuration force us to have what it need to build multi-platform images (Qemu in our tests).

That is why the tentative to fall back to a common one for all the ways to build (docker, podman, jib).

[tdiesler]

@rohanKanojia yes, this is with jib