Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add note about vddk secret namespace #4713

Merged
merged 4 commits into from
Nov 14, 2024
Merged

docs: add note about vddk secret namespace #4713

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bdbcb37
docs: add note about vddk secret namespace
arturshadnik Nov 14, 2024
b68e86f
ci: auto-formatting prettier issues
arturshadnik Nov 14, 2024
e241687
docs: code review
benradstone Nov 14, 2024
6b6a8bd
Merge branch 'master' into docs/vddk-secret-ns
benradstone Nov 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions ...s-content/vm-management/create-manage-vm/advanced-topics/migrate-vm-kubevirt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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, it will be automatically populated by Palette CLI.
benradstone marked this conversation as resolved.
Show resolved Hide resolved

<!--prettier-ignore-->
<details>
Expand Down Expand Up @@ -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.
benradstone marked this conversation as resolved.
Show resolved Hide resolved

Refer to the
[Pull an Image from a Private Registry documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/)
Expand Down