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

Use a Node's primary NIC as the secondary OVS bridge physical interface #5735

Closed
jianjuns opened this issue Nov 20, 2023 · 6 comments · Fixed by #6108
Closed

Use a Node's primary NIC as the secondary OVS bridge physical interface #5735

jianjuns opened this issue Nov 20, 2023 · 6 comments · Fixed by #6108
Assignees
Labels
area/interface Issues or PRs related to network interfaces area/ovs Issues or PRs related to OVS area/secondary-network Issues or PRs related to support for secondary networks in Antrea kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jianjuns
Copy link
Contributor

Describe the problem/challenge you have
In Antrea VLAN secondary network support (#5278), we require a separate NIC for the secondary OVS bridge's physical interface. However, it is quite common a K8s Node has only one NIC. So, the ask is to support using a Node's primary NIC (which is also the Antrea overlay network's transport interface) as the secondary bridge's physical interface.

Describe the solution you'd like
When a Node interface is configured for the secondary bridge, antrea-agent should move its IP addresses and routes to the secondary bridge after connecting the interface to the bridge, and it should also retore the IPs and routes before exits.

Moving an interface and its IPs/routes to an OVS bridge may not be compatible with all host network configurations and may not work well with other network managers.

@jianjuns jianjuns added kind/feature Categorizes issue or PR as related to a new feature. area/interface Issues or PRs related to network interfaces area/ovs Issues or PRs related to OVS labels Nov 20, 2023
@jianjuns
Copy link
Contributor Author

@meibensteiner create this issue to track your requirement.

@antoninbas antoninbas added the area/secondary-network Issues or PRs related to support for secondary networks in Antrea label Nov 20, 2023
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@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 19, 2024
@meibensteiner
Copy link

I would appreciate it if this was implemented at some point. :)

@jianjuns
Copy link
Contributor Author

I would appreciate it if this was implemented at some point. :)

Yes, we plan to support it in this release. @aroradaman is working on it.

@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 Feb 20, 2024
@meibensteiner
Copy link

Awesome. @aroradaman Id love to test it :)

@aroradaman
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/interface Issues or PRs related to network interfaces area/ovs Issues or PRs related to OVS area/secondary-network Issues or PRs related to support for secondary networks in Antrea kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants