Skip to content

Conversation

@ernado
Copy link
Contributor

@ernado ernado commented Mar 16, 2023

What type of PR is this?

/kind feature

What this PR does / why we need it:

Add riscv64 architecture support.

Special notes for your reviewer:

Previous attempt: #86011

Requires: kubernetes/release#2968
Requires: protocolbuffers/protobuf#12244, protocolbuffers/protobuf#12266

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 16, 2023
@k8s-ci-robot
Copy link
Contributor

Hi @ernado. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 16, 2023
@k8s-ci-robot k8s-ci-robot requested review from dims and jpbetz March 16, 2023 17:43
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ernado
Once this PR has been reviewed and has the lgtm label, please assign bentheelder for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@fedebongio
Copy link
Contributor

/triage accepted
please ping us when needs review

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 18, 2023
@ernado
Copy link
Contributor Author

ernado commented Apr 21, 2023

I'll close this PR until following dependencies are ready:

  • distroless image for riscv64
  • etcd image for riscv64
  • Kubernetes base images (in kubernetes/release)

Ref: kubernetes/release#2968

I will be maintaining forks and automated artifacts build for them under https://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.

@ernado ernado closed this Apr 21, 2023
@liggitt liggitt mentioned this pull request Mar 4, 2024
ncopa added a commit to ncopa/k0s that referenced this pull request May 14, 2025
Add patch that simply allows kubernetes to be built on riscv64.

ref: kubernetes/kubernetes#86011
ref: kubernetes/kubernetes#116686

Signed-off-by: Natanael Copa <[email protected]>
ncopa added a commit to ncopa/k0s that referenced this pull request May 14, 2025
Add patch that simply allows kubernetes to be built on riscv64.

ref: kubernetes/kubernetes#86011
ref: kubernetes/kubernetes#116686

Signed-off-by: Natanael Copa <[email protected]>
ncopa added a commit to ncopa/k0s that referenced this pull request May 15, 2025
Add patch that simply allows kubernetes to be built on riscv64.

ref: kubernetes/kubernetes#86011
ref: kubernetes/kubernetes#116686

Signed-off-by: Natanael Copa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants