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

CNI integration #14

Open
richardcase opened this issue Jun 28, 2021 · 12 comments
Open

CNI integration #14

richardcase opened this issue Jun 28, 2021 · 12 comments
Labels
kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@richardcase
Copy link
Contributor

richardcase commented Jun 28, 2021

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.

@richardcase richardcase transferred this issue from another repository Jun 28, 2021
@richardcase richardcase added area/reignite kind/feature New feature or request labels Jun 28, 2021
@richardcase richardcase added this to the Milestone 1 - re:ignite milestone Jun 28, 2021
@richardcase richardcase modified the milestones: v0.1.0, v0.2.0 Sep 9, 2021
@richardcase richardcase changed the title CNI integration in re:ignite CNI integration Oct 21, 2021
@richardcase richardcase added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Oct 27, 2021
@yitsushi
Copy link
Contributor

yitsushi commented Nov 4, 2021

@richardcase
Copy link
Contributor Author

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 was referenced Nov 4, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Jan 4, 2022

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2022
@richardcase
Copy link
Contributor Author

This is still needed.

@Callisto13 Callisto13 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
@Callisto13
Copy link
Member

https://youtu.be/Kvdh78TURck

@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 19, 2023
@yitsushi
Copy link
Contributor

Still valid.

@pablochacin
Copy link

pablochacin commented Oct 13, 2023

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?

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 14, 2023
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 15, 2023
@richardcase
Copy link
Contributor Author

@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.

@pablochacin
Copy link

Hi @richardcase Thanks for the update.

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 16, 2023
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Status: Backlog
Development

No branches or pull requests

4 participants