From 1fcc5f3ff799381f5495a32a96d404ce0812dde1 Mon Sep 17 00:00:00 2001 From: Matthew Garrell <> Date: Tue, 27 Apr 2021 08:39:11 -0400 Subject: [PATCH] JIRA CNV-10760 Adding information about referencing NAD definitions in different namespaces JIRA CNV-10760 Changes made based on SME review JIRA CNV-10760 Changes made based on peer review --- modules/virt-attaching-vm-secondary-network-cli.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/virt-attaching-vm-secondary-network-cli.adoc b/modules/virt-attaching-vm-secondary-network-cli.adoc index 9dd1cdf0109a..1ed4bca88e53 100644 --- a/modules/virt-attaching-vm-secondary-network-cli.adoc +++ b/modules/virt-attaching-vm-secondary-network-cli.adoc @@ -39,7 +39,7 @@ spec: pod: {} - name: bridge-net <1> multus: - networkName: <2> + networkName: <2> ... ---- <1> The name of the bridge interface. This value must match the `name` value of the corresponding `spec.template.spec.networks` entry. @@ -47,7 +47,7 @@ spec: + [NOTE] ==== -The example virtual machine is connected to both the `default` pod network and `bridge-net`, which is defined by a network attachment definition named `a-bridge-network`. +The example virtual machine is connected to both the `default` pod network and `bridge-net`, which is defined by a network attachment definition named `a-bridge-network`. If the network attachment definition is not in the same namespace as the VM, you must combine the namespace and the network name to create the network attachment definition name. ==== . Apply the configuration: