Closed wsilva closed 1 year ago
Hi @wsilva Thank you for reporting this issue.
Your suggestion makes sense.
We can build a multi-platform docker image by using docker buildx
.
The kube-rbac-proxy
container works because it image is already multi-platform.
Could you try to use the multi-platform images that I built in this draft, please?
Just add the following parameters in the helm upgrade --install
command:
--set operator.image.tag="feat-multi-platform-support" \
--set worker.image.tag="feat-multi-platform-support" \
--set scan.plugins.popeye.image.tag="v0.11.1-cross"
Below is the difference between the docker manifest inspect
command output for both images.
docker manifest inspect ghcr.io/undistro/zora/operator:v0.4.4
docker manifest inspect ghcr.io/undistro/zora/operator:feat-multi-platform-support
Wow, thanks. 🙇
You were faster than me. Also made the following PR: https://github.com/undistro/zora/pull/202 but I will close mine since yours is way more complete.
Will make some tests tomorrow and let you know.
Oh @wsilva I didn't know you were working on it.
Feel free to reopen your PR and we can work on it. Your contributions are welcome!
Feature Description
Ability to run in ARM architecture clusters like raspberries computers or AWS graviton instances
Is your feature request related to a problem?
Yeap, I can not run the zora operator into a arm cluster.
What alternatives have you considered?
Not sure if it's too complicated to compile the container entrypoint command and build the container image for multi architecture.
Additional Context
I have a "cluster" with 4 raspberries 3B and 2 raspberries zero w. We can disregard the Zero W models because they are have armv6l architecture that are not supported by Kubernetes or even Docker, I struggle to put then in a running cluster. But the 3B are running fine with a k3s cluster:
I can even install with the following command:
But the operator is not able to run:
The rbac proxy container is ok:
But the manager throws the following: