Enable CSI cloning functionality when CDI populators are disabled #3902
+236
−9
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.
This draft introduces an attempt to allow DataVolumes to use CSI volume cloning (instead of falling back to host-assisted clone strategy) even when the usePopulator feature is set to false, providing direct cloning for storage classes that support CSI clone operations.
added csi-clone support for both pvc and snapshot sources - withing the cloning process, PVC with a dataSource/dataSourceRef pointing to the pvc/volumesnapshot will be created.
What this PR does / why we need it:
Following our discussion about Portworx’s set of the userPopulator field to false, we decided to reintroduce the ability to perform a CSI-based clone even without CDI populators. This avoids falling back to host-assisted cloning, which significantly increases clone completion time.
Which issue(s) this PR fixes *
Jira Ticket: https://issues.redhat.com/browse/CNV-66958
for additional context:
The PR that removed csi-cloning after introducing CDI populators: 2285ceb#r1235350852
Special notes for your reviewer:
@alromeros
@akalenyu
Release note: