-
Notifications
You must be signed in to change notification settings - Fork 10
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
ARM Docker image #32
Comments
Hi, thanks for the issue. At this moment, we have not try to do this. it's not a priority for us. Anyway if you want to contribute to add arm image, we probably need to dive here https://sdk.operatorframework.io/docs/advanced-topics/multi-arch/ to make some change on pipeline github to build for multiple archs. Allowing nodeSelector can easily be add if needed https://github.com/InseeFrLab/helm-charts/tree/master/charts/s3-operator here. |
@alexisdondon I sumbited a PR. @reitermarkus Would you give us some insight about your usecase? Are you using this with Onyxia? Are you deploying on a Macbook? |
@garronej: I would be also be interested in having images that can run on Macbooks. My use case: for evaluation I run new software components on a local K3S cluster on my Macbook (ARM64) before moving on to any real environments running on AMD64. |
@FrankFoerster24 understood. |
I am not. I just came across your S3 operator randomly. |
My use case is a mixed cluster with some
No, just tried the S3 operator standalone. |
Many thanks to everyone here, both for submitting the issue and a solution (I just merged Joseph's PR). The image building action appears to have run without issue, could you confirm the built image is also working in your arm64 environment ? Also sorry for the lack of reactivity on our end ; as Alexis mentioned aboved, the maintenance of s3-operator is really low priority for us, which caused us to overlook the contributions here. |
Closing this as completed, hopefully the now-available ARM image is fully functional. |
Currently, no ARM image is available, resulting in
ImagePullBackOff
due toAdditionally, the Helm chart currently does not allow specifying a
nodeSelector
to prevent it from being scheduled on ARM nodes.The text was updated successfully, but these errors were encountered: