Description of problem: To make use of 802.3ad S-tag and C-tags, the linux bridge requires the option vlan-protocol set to 802.1ad, so it can add S-tags of ethertype 0x88A8 and does the correct forwarding. If this is set to 802.1Q (default, 0x8100), the bridge will drop the guest tagged frames as it tries to deliver locally (not supported). Currently, for this to work, the user needs to manually edit the bridge on each node: # nmcli con mod br1 bridge.vlan-protocol 802.1ad # nmcli con down br1 # nmcli con up br1 Its this setting that ends up changed with that. # cat /sys/class/net/br1/bridge/vlan_protocol This is probably a kubernetes-nmstate RFE, and depending if you want to set that manually like was done with vlan-filtering via script a while ago (I think?), an nmstate RFE too. But I'll leave these decisions to you to open the child RFE if you need.
Setting the target to future as this is waiting for an RFE on nmstate
Support for vlan-protocol will be added to nmstate in 9.1, so circa in OpenShift 4.14. Moving to the standalone operator to continue the tracking there.