From 64a037a4a8b9cbb3df2fa66b2c8bc6ae4a31d820 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ji=C5=99=C3=AD=20Herrmann?= Date: Thu, 7 Aug 2025 18:10:47 +0200 Subject: [PATCH] Updating vlan ID in localnet NAD Applied peer review --- modules/virt-creating-localnet-nad-cli.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/modules/virt-creating-localnet-nad-cli.adoc b/modules/virt-creating-localnet-nad-cli.adoc index df0bf0afd9c2..a06de8a26120 100644 --- a/modules/virt-creating-localnet-nad-cli.adoc +++ b/modules/virt-creating-localnet-nad-cli.adoc @@ -61,7 +61,8 @@ spec: "type": "ovn-k8s-cni-overlay", <3> "topology": "localnet", <4> "mtu": 1500, <5> - "netAttachDefName": "default/localnet-network" <6> + "vlanID": 200, <6> + "netAttachDefName": "default/localnet-network" <7> } ---- <1> The CNI specification version. The required value is `0.3.1`. @@ -69,7 +70,8 @@ spec: <3> The name of the CNI plug-in to be configured. The required value is `ovn-k8s-cni-overlay`. <4> The topological configuration for the network. The required value is `localnet`. <5> Optional: The maximum transmission unit (MTU) value. If you do not set a value, the Cluster Network Operator (CNO) sets a default MTU value by calculating the difference among the underlay MTU of the primary network interface, the overlay MTU of the pod network, and byte capacity of any enabled features, such as IPsec. -<6> The value of the `namespace` and `name` fields in the `metadata` stanza of the `NetworkAttachmentDefinition` object. +<6> Optionally, for more fine-grained network management, you can configure a virtual LAN (VLAN) ID for the NAD. VMs that use this NAD have an interface that can communicate only with devices that use the same VLAN ID (`200` in this example). +<7> The value of the `namespace` and `name` fields in the `metadata` stanza of the `NetworkAttachmentDefinition` object. . Apply the manifest: +