Skip to content
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

Add support for RISC-V #64

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

chazapis
Copy link

Since Helm does not provide riscv64 binaries yet, I use a separate Dockerfile that builds from source. I have already submitted a PR to Helm for releasing a RISC-V binary. When it is merged, the Dockerfile.riscv64 can be simplified.

The entry script has also been modified to function without Helm v2. Helm v2 is deprecated, a release has not been made for close to 3 years, and according to the documentation v2 charts can also be installed with Helm v3. The new entry script should function even when Helm v2 is required, but can also be easily modified to fail with an error.

The work is part of an ongoing effort to run K3s on RISC-V. In K3s, klipper-helm is used to install Traefik, which is part of the default deployment.

The resulting container image, built with ARCH=riscv64 make has been tested on QEMU and is working fine.

Signed-off-by: Antony Chazapis <chazapis@ics.forth.gr>
@chazapis
Copy link
Author

As recorded in the k3s-io/k3s#7778, most dependencies now support the riscv64 architecture, except klipper-helm and klipper-lb. It also seems that Rancher has started supporting RISC-V images, as is the case with Local Path Provisioner.

I have updated this PR, as the base Alpine image now also supports RISC-V, so there is no need to use another container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant