Antony Chazapis

> LGTM > @Anarkis do we have RISC-V machines for building? There is no need to build natively on RISC-V. The patch sets `GOARCH` to cross-compile a binary. This seems...

@derekbit, @Anarkis, @pgonin Sorry to bother you, but it has been over 3 months with no response. This is a really helpful feature that requires no code changes. Could it...

While we have some hardware in our lab, we generally use QEMU for testing on RISC-V. However, I am not sure how this would tie up with running the CI...

@derekbit, I think it is worth trying to include a RISC-V image in each release. As local-path-provisioner is meant to run in containerized form within Kubernetes, it is not really...

Yes, I agree that the backwards compatibility is concerning, but this is really useful for new deployments. For that reason, I have not changed the sample configuration file. As it...

@matttrach, @galal-hussein, @brandond Sorry to bother you, but it has been over 3 months with no response. This is a really helpful feature that requires no code changes. Could it...

@brandond, I understand. Thank you for the feedback. I just want to stress out that even though the RISC-V community is still small, it is constantly growing. Having this project...

Almost a year later, the tides are changing. As recorded in the [K3s on RISC-V PR](https://github.com/k3s-io/k3s/pull/7778), most dependencies now support the `riscv64` architecture, except klipper-helm and klipper-lb. It also seems...

As recorded in the https://github.com/k3s-io/k3s/pull/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...

Also note that this uses a prepackaged k3s-root we have manually compiled ~and have available on GitHub~ (edit: removed, as the PR has been merged in k3s-root). Once the [relevant...