Goal

Virtual Machine templates are traditionally pre-configured virtual machines that serve as blueprints for creating new VMs. They encapsulate the operating system, installed software, and configuration settings, allowing for the rapid and consistent deployment of virtual machines. Using templates streamlines the VM creation process, reduces errors, and ensures uniformity across the virtualized environment.

User Storie

• As a VirtualMachine owner I would like to create a VirtualMachine from a native in-cluster template that
  • can be hosted in a separate namespace
  • tracks a periodically updated golden image
  • was originally created from a VirtualMachine that had customisation
• As a VirtualMachine owner I would like to share my native in-cluster templates between namespaces I control

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.
• Sealing / generalizing existing VMs before creating a template from them.
• As a VirtualMachine owner I would like to import and export my native in-cluster templates between clusters into namespaces that I control

Notes

• Any additional details or decisions made/needed
• This feature will be Tech Preview in 4.22
• Deployment should be an automated process in 4.22
• Continuation of https://issues.redhat.com/browse/CNV-58913