On MacOS (M2) ... <div class="snippet-clipboard-content notranslate position-relat

PR: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id

Is a dependency of <a class="issue-link js-issue-link" data-error-text="Failed to load

Install operator image according to the target architecture about camel-k HOT 7 CLOSED

tdiesler commented on June 17, 2024

Install operator image according to the target architecture

from camel-k.

Comments (7)

gansheer commented on June 17, 2024

If this is an arm64 architecture processor you should follow the installation documentation. The Kamel CLI defaults to x86 image so you need to set the arm64 operator image explicitly, and the integration base image as well.

from camel-k.

tdiesler commented on June 17, 2024

merci, that worked

from camel-k.

tdiesler commented on June 17, 2024

Do we already have an issue about improving the getting started experience on ARM64?

Currently I do ...

> minikube start --addons registry

> CAMEL_K_VERSION=2.2.0
> kamel install --olm=false --operator-image apache/camel-k:${CAMEL_K_VERSION}-arm64 --base-image eclipse-temurin:17-jdk@sha256:a90cec83bb9b9ab19a63e377b20c3aa4e076b16c52d36e83c62c451b6d034e22

> kubectl logs -l camel.apache.org/component=operator --tail=400 -f

> kamel run helloworld.groovy
> kubectl logs -l camel.apache.org/integration=helloworld --tail=10 -f

from camel-k.

tdiesler commented on June 17, 2024

PR: #5200

$ go run ./cmd/kamel install                                                                                                            
OLM is not available in the cluster. Fallback to regular installation.
Using arch specific operator image: docker.io/apache/camel-k:2.3.0-SNAPSHOT-arm64
Using arch specific base image: eclipse-temurin:17@sha256:a90cec83bb9b9ab19a63e377b20c3aa4e076b16c52d36e83c62c451b6d034e22
Camel K installed in namespace default

from camel-k.