-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
pvc-source-for-dataimportcron
-
Product / Portfolio Work
-
False
-
-
False
-
- A PVC from any namespace can be the source for a DataImportCron
- Update detection when PVC is replaced
- Tier-1 testing
- u/s and d/s documentation updated
-
None
-
Green
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
As an OpenShift integrator I want to use a PVC from an arbitrary namespace as a "source" for DataImportCron "imports" so that I can implement a storage-agnostic "golden image" VM provisioning capability that uses a cluster-provisioned VM as input.
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue | <link to GitHub Issue> |
| DEV | Upstream code and tests merged | https://github.com/kubevirt/containerized-data-importer/pull/3617 |
| DEV | Upstream documentation merged | <link to meaningful PR or GitHub Issue> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| QE | Test plans in Polarion | https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-11828 |
| QE | Automated tests merged | Covered in: https://github.com/kubevirt/containerized-data-importer/pull/3617 |
| DOC | Downstream documentation merged | https://github.com/openshift/openshift-docs/pull/94142 |
