-
Epic
-
Resolution: Done
-
Normal
-
None
-
DevPreview: Upload image from cluster to registry
-
-
Green
-
In Progress
-
CNV-8322 - Integration with OpenShift Tekton Pipelines
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
When a user runs our example pipelines (windows installer, windows customize), the newly created image is only in a single cluster. The created image can be needed in different clusters, and thus we should provide a way how to push the new images in different registries. We can reuse [1] functionality and maybe container disks automation.
[1] https://kubevirt.io/user-guide/operations/export_api
User Stories
- As a platform engineer (or developer) I would like to push the image to a registry, so other users/cluster can use it.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| 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 | <link or reference to Polarion> |
| QE | Automated tests merged | <link or reference to automated tests> |
| DOC | Downstream documentation merged | <link to meaningful PR> |
- blocks
-
-
- In Progress
-
- is related to
-
-
- In Progress
-
-
-
- Closed
-
- is triggering
-
CNV-32773 Allow specifying download format in vmexport
-
- Closed
-
- links to