From c87c49279686b5a812be59d71ff83db5a90861c6 Mon Sep 17 00:00:00 2001 From: Sabrina Jess Date: Wed, 16 Mar 2022 15:51:11 -0400 Subject: [PATCH] minor edit --- modules/virt-creating-bridge-nad-cli.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/virt-creating-bridge-nad-cli.adoc b/modules/virt-creating-bridge-nad-cli.adoc index fb78653b59..e50c75d544 100644 --- a/modules/virt-creating-bridge-nad-cli.adoc +++ b/modules/virt-creating-bridge-nad-cli.adoc @@ -38,7 +38,7 @@ spec: }' ---- <1> The name for the `NetworkAttachmentDefinition` object. -<2> Optional: Annotation key-value pair for node selection, where `bridge-interface` is the name of a bridge configured on some nodes. If you add this annotation to your network attachment definition, your virtual machine instances will only run on the nodes that have the `bridge-interface` bridge connected. +<2> Optional: Annotation key-value pair for node selection, where `bridge-interface` must match the name of a bridge configured on some nodes. If you add this annotation to your network attachment definition, your virtual machine instances will only run on the nodes that have the `bridge-interface` bridge connected. <3> The name for the configuration. It is recommended to match the configuration name to the `name` value of the network attachment definition. <4> The actual name of the Container Network Interface (CNI) plug-in that provides the network for this network attachment definition. Do not change this field unless you want to use a different CNI. <5> The name of the Linux bridge configured on the node.