arm64 support for CI/CD in k8s (OD-1515)

First of all thanks for all the improvements.

I'm trying to test the pipelines for CI/CD (k8s) and I don't know if it's a bug or I have a problem in my setup. I install OneDev on arm64 (OCI Ampere + k3s with containerd) without any problems. But when I want to test a Job Executor, I got a kubectl error. I solved installing arm64 version of kubectl in the OneDev pod , and then get stuck with an jdk error.

Please wait...
Checking access to the cluster...
Preparing job (executor: k8s, namespace: k8s-executor-test)...
Running job on node labs.ueii.net...
Starting job containers...
2023-08-23T20:14:00.879866929-03:00 exec /usr/local/openjdk-11/bin/java: exec format error

I looked into the pod the jdk binary but i don't found it. The CI/CD platform is optimized to work on AMD64? or there is something I can tweak or change in order to get everything working? Thank you so much

Robin Shen commented 2 years ago

@carlospalavecino thanks for trying out OneDev. Yes CI/CD on k8s currently works for amd64 arch only, will make it work on arm64 soon.

Robin Shen changed title 2 years ago

Previous Value	Current Value
Unable to create a job executor on arm64 (OCI alpine)	arm64 support for CI/CD in k8s

Robin Shen changed fields 2 years ago
Name Previous Value Current Value
Type

Support Request

Improvement
OneDev changed state to 'Closed' 2 years ago
Previous Value Current Value
Open

Closed
OneDev commented 2 years ago

State changed as code fixing the issue is committed (01ce1f56)
OneDev changed state to 'Released' 2 years ago
Previous Value Current Value
Closed

Released
OneDev commented 2 years ago

State changed as build #4028 is successful
Carlos Palavecino commented 2 years ago
It's amazing the commitment you show and the time response you manage, I`m really grateful. If at any time I can collaborate with something let me know, I am a Sr designer and rookie developer in case you need help. Thanks again.

Beyond the praise (you deserve) I installed onedev on an amd64 platform, but the new version that you released HELM 9.0.2 has an error in the kubectl binary.

root@onedev-0:/# kubectl version /usr/local/bin/kubectl: line 1: syntax error near unexpected token `<' /usr/local/bin/kubectl: line 1: `<?xml version='1.0' encoding='UTF-8'?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Details>No such object: kubernetes-release/release/v1.28.1/bin/kubectl</Details></Error>'

A fresh download of kubectl v1.25.12 fix the problem. I don`t know if it's a binary bug or the update.
Robin Shen commented 2 years ago

@carlospalavecino thanks for willing to help, and thanks for reporting the issues. The problem of corrupted kubectl is fixed in build #4031, please give it a try.
Carlos Palavecino commented 2 years ago

It's working now, thanks again
Login to comment

Name	Previous Value	Current Value
Type	Support Request	Improvement

Previous Value	Current Value
Open	Closed

Previous Value	Current Value
Closed	Released

Type	Improvement
Priority	Normal
Assignee	Robin Shen
Labels	No labels

Issue Votes (0)

Watchers (3)

Reference

OD-1515