-
Notifications
You must be signed in to change notification settings - Fork 307
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
[FEATURE] Add VLAN network for VM to support multiple or all VLANID #766
Comments
Using ovs instead of bridge seems better |
Harvester in Harvester can‘t also support bond. |
Note: once CNI bridge accept the patch[3] to support vlan trunk, and we can start to patch network-controller to support vlan networks [1] https://elixir.bootlin.com/linux/latest/source/net/bridge/br_vlan.c#L601 |
Any news regarding this? It would be nice to have an option like VMware's VLANID 4095 |
Currently, Bridge CNI Plugin didn't support VLAN trunk mode for Pods. |
ovs would support it, like @futuretea mentioned |
It will take some effort to change CNI plugin. |
Thank you! |
The upstream bridge PR containernetworking/plugins#829 is merged, we may continue our investigation about this, thanks. |
Hope this could be implemented soon, now my opnsense dhcp is a mess. The dhcp on one port is able to reach clients connected through other ports, as if they were internally connected. |
Is your feature request related to a problem? Please describe.
When building Harvester in Harvester, the inner Harvester's VLAN network will be ineffective, because the veth on the host end (outer Harvester host) only allows package with only one VLAN tag.
Describe the solution you'd like
There are two possible solutions.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: