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

Update .goreleaser.yml with Linux riscv64 binaries #2979

Closed
wants to merge 1 commit into from

Conversation

nickolaev
Copy link

There are lots of boards with riscv64 architecture available. We can argue if this architecture is more popular accessible than s390x for example. Let's generate the binaries for its Linux OS.

There are lots of boards with riscv64 architecture available. We can argue
if this architecture is more popular accessible than s390x for example.
Let's generate the binaries for its Linux OS.

Signed-off-by: Nikolay Nikolaev <nicknickolaev@gmail.com>
@derailed
Copy link
Owner

@nickolaev Thanks for the heads up!
K9s does it's best to align with k8s available platforms. Best I can tell, I don't think k8s targets this architecture?

@nickolaev
Copy link
Author

Indeed, there is no "support" out of the box. However:

  • K9s can be used on a board to manage a cluster remotely, no need to have it locally
  • We have a PoC port of KinD that was able to utilize K9s to browse the local resources
  • The architecture is gaining more and more popularity and surely will become widely spread at some point

@derailed derailed added the question Further information is requested label Nov 29, 2024
@derailed
Copy link
Owner

@nickolaev There are some scenarios where k9s shells out and expect kubectl to be present. Eventually we will remove this dependency in k9s core, however lots of plugins expect kubectl and affiliates present on the shell.

@nickolaev
Copy link
Author

Makes sense. Will close it now.

@nickolaev nickolaev closed this Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants