Goal

A tekton pipeline can create updated windows container disk. This way windows base images could be shared inside the an organization.

User Stories

• As a employee, I want to create a new Windows VM from a base image, so that I can try how Windows works in CNV.
• As a QE, I want to use an updated Windows base image, so that I am confident that Windows guests works for customers who has the most recent windows updates installed.
  • The pipeline will be based on windows-efi-installer pipeline https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-efi-installer. 
  • each Windows OS will use different ConfigMap with autounattend.xml file. Via this file, the windows will be configured to contains all necessary SW and drivers
  • Result of each spike should be powershell script, which will be part of autounattend.xml file.
  • Requirements for each Windows disk is described here: https://docs.google.com/document/d/1LTZeAnKVD05zOTcjQo4svSCvSPQy7ZXOcf_QJDgwjoE/edit,
  • The result disk should be stored here: https://cnv-qe-artifactory.apps.ocp-virt.prod.psi.redhat.com/artifactory/cnv-qe-server-local/cnv-tests/windows-images/

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• https://quay.io/repository/openshift-cnv/containerdisks?tab=tags provides already windows images, but they are mostly outdated because there is no automation to keep them updated.
• It should be build in a way that the a similar automation (pipeline and example config data) can be published after finishing this epic.