-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
- PR merged with set of provisioners switching over to CSI clones following research
- Unit tests
-
-
-
Storage Core Sprint 235, Storage Core Sprint 236, Storage Core Sprint 237, Storage Core Sprint 238, Storage Core Sprint 239, Storage Core Sprint 240
-
None
As a CNV administrator I want to see which cloning strategy is preferred for a given storage class by observing this information in the StorageProfile status. I want to override it by updating the spec.
As a CNV adminstrator I want the csi-snapshot-based pvc cloning strategy to be explicitly mentioned in the storage profile when it will be the default strategy attempted. I want all storage profiles to show the preferred strategy.
Today snapshot clone is used implicitly when we find a volumesnapshot class associated with a given storage class. We should be more explicit about whether we prefer a csi-snapshot, csi-clone, or host-assisted clone when using our smart cloning. This will make it easier to point out misconfiguration (ie. missing volumesnapshotclass object when we expect there to be one).
Note that this does not apply to the explicit clone from snapshot source api that akalenyu is working on. This is about "smart clone" (the 'pvc' DataVolume source).