Add documentation for VolumeNamePolicy and PrefixTargetName VolumeRestorePolicy#986
Open
lyarwood wants to merge 1 commit intokubevirt:mainfrom
Open
Add documentation for VolumeNamePolicy and PrefixTargetName VolumeRestorePolicy#986lyarwood wants to merge 1 commit intokubevirt:mainfrom
lyarwood wants to merge 1 commit intokubevirt:mainfrom
Conversation
…torePolicy
Document the new VolumeNamePolicy field on VirtualMachineClone and the
PrefixTargetName policy for both VirtualMachineClone and
VirtualMachineRestore. PrefixTargetName generates predictable PVC names
using {targetVMName}-{volumeName}, providing a deterministic alternative
to RandomizeNames while avoiding collisions across targets.
Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Lee Yarwood <lyarwood@redhat.com>
kubevirt-bot
added
the
dco-signoff: yes
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
akalenyu
reviewed
Apr 9, 2026
|
|
||
| ### Volume name policy | ||
|
|
||
| The `volumeNamePolicy` field controls how volumes are named during the clone operation. Under the hood, this is converted to a `volumeRestorePolicy` on the `VirtualMachineRestore` created by the clone controller. |
Contributor
There was a problem hiding this comment.
How this works under the hood is theoretically always subject to changes, though somewhat unlikely in this case. Just a thought
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
volumeNamePolicyfield onVirtualMachineClone, coveringRandomizeNames(default) andPrefixTargetNamepolicies with a YAML examplePrefixTargetNameas a third option under the existing volume restore policies section of the snapshot/restore docsPrefixTargetNameas an alternative toInPlacefor predictable volume namingRelated PRs