-
Epic
-
Resolution: Done
-
Major
-
None
Goal
Provide an end-to-end flow for creating a VM, moving it to a (Git?) repository and then deploy it on multiple clusters using ACM. This should support VMs with multiple disks, secrets, CM etc.
User Stories
- As an admin I would like to know how to get a VM with all of it's configurations (disks, secrets, CM etc.) to an external repository. This process may require sysprep
- As a ACM admin I would like to be able to deploy the VM definition to multiple clusters (including disks, secrets, CM etc.)
- As a ACM admin I would like to be able to update the VM definition to multiple clusters
- The VM disk image which is tested in one cluster, is deployed to other clusters.
- Starting with a single VM, multiple VMs would be nice to have.
Non-Requirements
- We are not sure if downstream code would contain required functionality, so we cannot promise downstream qe.
Notes
- This is about VM definitions only, not for templates
Done Checklist
Who | What | Reference |
---|---|---|
DEV | Upstream roadmap issue (or individual upstream PRs) | https://github.com/0xFelix/gitops-demo |
DEV | Upstream documentation merged | https://github.com/kubevirt/user-guide/pull/674 |
DEV | gap doc updated | |
DEV | Upgrade consideration | |
DEV | CEE/PX summary presentation | |
QE | Test plans in Polarion | |
QE | Automated tests merged | |
DOC | Downstream documentation merged | https://cloud.redhat.com/blog/using-red-hat-advanced-cluster-management-and-openshift-gitops-to-manage-openshift-virtualization https://drive.google.com/file/d/1ykGTibz8Nn7JmVt3Uz7pJ9FzmGG3BQz6/view?usp=share_link |