-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Trunk ports support for OVN
-
5
-
False
-
-
False
-
-
rhel-9
-
rhel-net-ovn
-
100% To Do, 0% In Progress, 0% Done
-
ssg_networking
This epic tracks all the effort needed to deliver the solution related to the feature request described below.
Today it is possible to pass the full trunk into the workload by using the `other_config : vlan-passthru` logical switch option (a boolean).
Still, we'd like to have better granularity: we need to be able to specify which VLAN tags trickle down to a specific workload.
Other projects have come up w/ a similar APIs:
- bridge CNI: https://www.cni.dev/plugins/current/main/bridge/#example-l2-only-vlan-configuration
- OVS CNI: https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/docs/cni-plugin.md#example-configuration
- nmstate: https://nmstate.io/kubernetes-nmstate/examples.html#linux-bridge
- blocks
-
CORENET-5642 Trunk ports support for OVN Kubernetes localnet
-
- New
-
-
RFE-6831 Support trunk ports with OVN Kubernetes localnet
-
- Backlog
-
-
CORENET-5768 Granular trunk port support for OVN Kubernetes localnet
-
- To Do
-