1. Proposed title of this feature request

Support trunk ports with OVN Kubernetes localnet

2. What is the nature and description of the request?

Users can use localnet to connect to the native network, or to a selected VLAN. Make it possible to subscribe to a full trunk or a subset of VLANs.

Similar API on bridge CNI: https://www.cni.dev/plugins/current/main/bridge/#example-l2-only-vlan-configuration

Similar API on OVS CNI: https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/docs/cni-plugin.md#example-configuration

3. Why does the customer need this? (List the business requirements here)

Customers want to connect their VMs to an underlying physical network with a trunk, so they can then listen to multiple VLANs on a single interface and handle the untagging themselves.

This functionality is available in Bridge CNI and OVS CNI already. However, OVN Kubernetes localnet only supports connecting to a single VLAN. Since we are recommending localnet as the go-to network solution for physical network access, we should make sure it has feature parity with the other basic CNIs.

4. List any affected packages or components.

OVN Kubernetes