New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test ARM64 architecture - operator and builder pods #4519
Comments
I managed to deploy camel-k 2.0 on an arm64 using camel-k-client-2.0.0-linux-arm64.tar.gz on a Raspberry 4 (with ubuntu server + minikube + docker). My feedback is:
This behavior could be the result of an incomplete kubernetes configuration on my minikube. Or it could also be a result of : Still, with these modifications I managed to run successfully a basic integration. |
Working with camel-k 2.0.0, 2.1.0 and 2.2.0nightly on OCI arm64 cluster (Ampere A1 nodes). kamel install --operator-image=apache/camel-k:2.1.0-arm64 --base-image=docker.io/eclipse-temurin:17.0.9_9-jre@sha256:e530452bd0b0678cdcbb86d2fe86bbee6a2972c723c8040ccc00ca64c76df0ba Further evidences needed, please let me know, would be happy to share. |
Thanks for sharing! @niamR are you using the default publishing strategy (Spectrum) or any other strategy by any chance? |
@gansheer maybe the configuration above could be something we should document in the official doc page? we may also have a look at github actions as in https://github.blog/2023-10-02-introducing-the-new-apple-silicon-powered-m1-macos-larger-runner-for-github-actions/ and see if we are able to add a simple smoke test as well. |
@squakez Both are great ideas. I'll look into it. |
@squakez Only tested with default so far, but I can give a try with buildah as we were using it in earlier versions. |
No thanks, buildah was deprecated so it does not make sense. I was speaking with @gansheer right now on fixing the documentation. For now it was good enough you manage to test and provide the feedback it's working, thanks a lot! |
We need to test the work done in a ARM64 Kubernetes cluster.
Originally posted by @squakez in #4148 (comment)
The text was updated successfully, but these errors were encountered: