-
Notifications
You must be signed in to change notification settings - Fork 70
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
Arm Support #260
Comments
Hello, could you try removing or overriding the GOARCH variable here https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/cmd/Dockerfile#L12, and then compiling? Perhaps that may help. Is it crashing immediately on start or only after a while? If I remember correctly, you should be able to change the log level in the manifest: https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/manifests/ovs-cni.yml.in#L63 |
I ran into this as well. Changing Is there any interest in releasing official arm64 binaries? |
I opened PR #266 to at least make the plumbing for building arm64 easier. For now I am able to use this for my needs, but it would be nice to have this extended to release official binaries for both architectures. |
#266 was merged, which at least makes it possible to build for arm64. Perhaps there is interest in releasing multiple official binaries? |
I would not be against it. Currently I just manually tag, call |
Can we release arm64 assets in https://github.com/k8snetworkplumbingwg/ovs-cni/releases? |
It seems |
full ARM support was added in #307 multiarch image (amd64/arm64/ppc64le) is available in Github package registry https://github.com/k8snetworkplumbingwg/ovs-cni/pkgs/container/ovs-cni-plugin |
Hello, is OVS-CNI usable for arm nodes? I noticed that it was crosscompiled to work for the arm environment, however, I'm getting an issue where the OVS CNI pods are crashing randomly only for my arm nodes.
The only error that's visible on the pod is as follows:
Is there a way to get more verbose logging options to determine where it had a segfault?
Thanks so much!
The text was updated successfully, but these errors were encountered: