Document URL:
https://docs.openshift.com/container-platform/4.13/virt/virtual_machines/vm_networking/virt-attaching-vm-multiple-networks.html#virt-creating-linux-bridge-nad-cli_virt-attaching-vm-multiple-networks

Section Number and Name:
Creating a Linux bridge network attachment definition in the CLI

Describe the issue:
Due to https://bugzilla.redhat.com/show_bug.cgi?id=2179333, any VM connected to a VLAN through a bridge CNI NAD is also connected to the native VLAN 1. This is unintended. We should make sure our users set `"preserveDefaultVlan": false` to prevent this from happening.

Suggestions for improvement:
Change the current example:
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: <bridge-network>
annotations:
k8s.v1.cni.cncf.io/resourceName: bridge.network.kubevirt.io/<bridge-interface>
spec:
config: '

{ "cniVersion": "0.3.1", "name": "<bridge-network>", "type": "cnv-bridge", "bridge": "<bridge-interface>", "macspoofchk": true, "vlan": 1 }

'
To:
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: <bridge-network>
annotations:
k8s.v1.cni.cncf.io/resourceName: bridge.network.kubevirt.io/<bridge-interface>
spec:
config: '

{ "cniVersion": "0.3.1", "name": "<bridge-network>", "type": "cnv-bridge", "bridge": "<bridge-interface>", "macspoofchk": true, "vlan": 1, "preserveDefaultVlan": false }

'

Additional information:
This should be changed on all releases starting with 4.12.
The backend bug where this new attribute was introduced: https://bugzilla.redhat.com/show_bug.cgi?id=2179333