docs: add note about vddk secret namespace (#4713)

* docs: add note about vddk secret namespace Signed-off-by: Artur Shad Nik <[email protected]> * ci: auto-formatting prettier issues * docs: code review --------- Signed-off-by: Artur Shad Nik <[email protected]> Co-authored-by: arturshadnik <[email protected]> Co-authored-by: Ben Radstone <[email protected]>
spectrocloud · Nov 14, 2024 · a8526fb · a8526fb
1 parent 24b9b3e
commit a8526fb
Showing 1 changed file with 3 additions and 2 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
@@ -88,7 +88,8 @@ from VMware vSphere to Palette VMO.
     documentation for guidance.
   - The migration host must have access to your image registry.
   - If you are using a private image registry, you must create a Secret to be used for the migration. The Secret must be
-    in the form of a YAML file and the `metadata.name` value must be `vddk-image-pull-secret`.
+    in the form of a YAML file and the `metadata.name` value must be `vddk-image-pull-secret`. The `metadata.namespace`
+    value should be left blank or omitted, as the Palette CLI will automatically populate it.
 
     <!--prettier-ignore-->
     <details>
@@ -130,7 +131,7 @@ from VMware vSphere to Palette VMO.
     ```
 
     You can then use this output to create your own Secret manually. Ensure that the `metadata.name` is set to
-    `vddk-image-pull-secret`.
+    `vddk-image-pull-secret`, and the `metadata.namespace` is left blank or omitted.
 
     Refer to the
     [Pull an Image from a Private Registry documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/)