[
https://issues.apache.org/jira/browse/CAMEL-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912837#comment-17912837
]
Thomas Diesler edited comment on CAMEL-21613 at 1/14/25 11:30 AM:
------------------------------------------------------------------
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
<!-- Supported only when using the jib build strategy -->
<createImageOptions>
<platform>linux/amd64</platform>
<platform>linux/arm64</platform>
</createImageOptions>
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift. All stuff must
work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
was (Author: tdiesler):
To remind myself ... we default to build strategy Jib and have this in the
templates ...
{code}
<!-- Supported only when using the jib build strategy -->
<createImageOptions>
<platform>linux/amd64</platform>
<platform>linux/arm64</platform>
</createImageOptions>
{code}
See 'jkube.container-image.platforms' in
https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#build-configuration.
Our general focus should be on easy entry for Camel to K8s i.e. local k8s
first, then your favourite free distro e.g. k3s, then OpenShift - all stuff
must work on OpenShift.
I use DockerDesktop Kubernetes and, which allows me to build for both amd64,
arm64. On a remote server, I have not yet seen an arm64 node.
So, yes. Defaulting to the local platform should be fine because it is
guaranteed to work on "local k8s". Building for an alternative platform should
be easy too.
How would you like to configure that? The container trait perhaps?
> Camel-Jbang Kubernetes Plugin: allow to choose image platform options
> ---------------------------------------------------------------------
>
> Key: CAMEL-21613
> URL: https://issues.apache.org/jira/browse/CAMEL-21613
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Gaelle Fournier
> Assignee: Thomas Diesler
> Priority: Minor
>
> We should be able to configure for which architecture platform(s) we cant to
> build the container.
>
> Currently we build the container image (with docker, JIB or podman) for both
> linux/amd64 and linux/arm64. That mean we need the user to be able to do
> multi-platform build.
> While it is available out of the box for JIB (and maybe podman), for docker
> it requires some specific tools like Qemu/buildx. We need to allow the user
> to override the default configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
