docs: PLT-1405 (#4066) (#4104)

* docs: PLT-1405 * docs: removed prettier comment * chore: vale feedback * docs: feedback from Tyler * docs: apply suggestions from code review Co-authored-by: caroldelwing <[email protected]> --------- Co-authored-by: caroldelwing <[email protected]> (cherry picked from commit ddded8e) Co-authored-by: Karl Cardenas <[email protected]>
spectrocloud · Sep 30, 2024 · 3ad619b · 3ad619b
1 parent b806745
commit 3ad619b
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/...s-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md b/...s-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md
@@ -22,6 +22,11 @@ from VMware vSphere to Palette VMO.
 - Only VMs whose operating systems are included under
   [`virt-v2v` supported guest systems](https://libguestfs.org/virt-v2v-support.1.html) can be migrated.
 
+- The network type <VersionedLink text="Multus CNI" url="/integrations/packs/?pack=cni-multus" /> requires a Network
+  Attachment Definition (NAD) to exist in the migration target namespace in the destination cluster. The NAD name must
+  also match the name assigned to the migration. The migration name is assigned during the wizard, which is started by
+  the Palette CLI's `vmo migrate-vm` command.
+
 ## Prerequisites
 
 - A Healthy VMO cluster. Refer to the [Create a VMO Profile](../../create-vmo-profile.md) for further guidance.