- Notifications
You must be signed in to change notification settings - Fork526
feat: support riscv64#2968
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Welcome@ernado! |
Hi@ernado. Thanks for your PR. I'm waiting for akubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listedhere. Instructions for interacting with me using PR comments are availablehere. If you have questions or suggestions related to my behavior, please file an issue against thekubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR isNOT APPROVED This pull-request has been approved by:ernado The full list of commands accepted by this bot can be foundhere. Needs approval from an approver in each of these files: Approvers can indicate their approval by writing |
ernado commentedApr 21, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I'll close this PR until following dependencies are ready:
I will be maintaining forks and automated artifacts build for them underhttps://github.com/go-riscv organization. Anybody interested in brinding riscv64 to k8s are welcome and can track progress there. My ETA is 2025, when debian will be released with full riscv64 support, or Q4 2023 if distroless will accept sid(unstable debian)-based images or riscv64 support can be added after current debian code freeze. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Support for riscv64 architecture.
Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?