# 20230302_Kubevirt-Roundup FCOS Tracker issue with kubevirt platform request: - https://github.com/coreos/fedora-coreos-tracker/issues/1126 Previous work (merged PRs): - https://github.com/coreos/coreos-assembler/pull/2750 - https://github.com/coreos/ignition/pull/1334 - https://github.com/coreos/afterburn/pull/725 - https://github.com/coreos/stream-metadata-rust/pull/24 - https://github.com/coreos/stream-metadata-go/pull/41 - https://github.com/coreos/fedora-coreos-tracker/pull/1144 Work in Progress PRs that weren't finished: - https://pagure.io/fedora-web/websites/pull-request/241 - https://github.com/coreos/fedora-coreos-pipeline/pull/514 - https://github.com/coreos/fedora-coreos-pipeline/pull/515 - https://github.com/coreos/fedora-coreos-docs/pull/394 Remaining work: - Verify existing work is valid - cosa buildextend-kubevirt - does it work? - can we use it and the pending docs to run a VM in kubernetes/openshift? - Make any necessary updates since we are publishing an ociarchive - The current rationale is out of date: - https://github.com/coreos/fedora-coreos-tracker/blob/ff0056385c428c26359b5739ec2fdf8e1985d27f/metadata/stream/rationale.yaml#L95 - May need to also update - https://github.com/coreos/stream-metadata-rust/pull/24 - https://github.com/coreos/stream-metadata-go/pull/41 - Add kubevirt to list of x86_64 artifacts to get built by the pipeline - update https://github.com/coreos/fedora-coreos-pipeline/blob/9251e20257b4ba300f7e61e461ff904d10507df1/config.yaml#L71 - Push Kubevirt container image to quay - When to push? - Probably in "cloud upload" step - However, maybe to a staging repo, then promote it in the release job. - Where to push? - For FCOS: `quay.io/fedora/fedora-coreos-kubevirt`? - For RHCOS: ? - Add docs - Can mostly just use https://github.com/coreos/fedora-coreos-docs/pull/394 - Add pipeline testing (follow on work, not a requirement up front) - kola-kubevirt job that tests kubevirt image in a given openshift cluster - can we use our `fedora-coreos-pipeline` OpenShift cluster for this? - does it support CNV (which is the product name for kubevirt)