-
Notifications
You must be signed in to change notification settings - Fork 37
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
CNI integration #14
Comments
Yeah there are a few plugins. With #13 we need to look at what plugins there are for macvtap and come up with a recommendation. When i looked back in April there was a difference in functionality and activity in the plugins i found. |
This issue is stale because it has been open 60 days with no activity. |
This is still needed. |
This issue is stale because it has been open 60 days with no activity. |
Still valid. |
I'm Interested. I'll do some research to understand how networking is done now. Is there any documentation about what is intended with this integration? |
This issue is stale because it has been open 60 days with no activity. |
@pablochacin - we currently use netlink directly to create the interfaces (tap or macvtap). We also support attaching to a bridge. The Firecracker Go SDK support using CNI. However, thats good for Firecracker but won't cover Cloud Hypervisor. So we probably need to integrate with CNI directly in Flintlock. |
Hi @richardcase Thanks for the update. |
This issue is stale because it has been open 60 days with no activity. |
@richardcase I'm revisiting this issue. I noticed #856 Does it affect the scope of this issue? My guess is that not, but wanted to check your thought about this. |
I don't think it affects the scope of the issue. We are going to remove macvtap from the firecracker side as we can't keep using our own fork of Firecracker. Let me know if i can help with anything. |
@richardcase can please assign it to me? |
Thanks @yitsushi , all yours @pablochacin |
Integrate CNI into flintlock so that the network interfaces on the host are created/configured via CNI. We need to expose this via the API and also provide a default config.
The text was updated successfully, but these errors were encountered: