Is your feature request related to a problem? Please describe.
Kubespray currently maintains its own KubeVirt image list https://github.com/kubernetes-sigs/kubespray/blob/master/test-infra/image-builder/roles/kubevirt-images/defaults/main.yml and build flow (see kubespray issue #12383). We’re trying to reuse a shared path in kubernetes-sigs/image-builder instead of maintaining a separate CI job and image definitions.
Right now, image-builder’s KubeVirt path is tied to QEMU targets and only covers a subset of the OSes Kubespray uses.
Missing OSes from the Kubespray KubeVirt list include:
- ubuntu-2004
- fedora-37, fedora-38, fedora-39, fedora-40, fedora-41, fedora-42
- fedora-coreos
- centos-8
- almalinux-8, almalinux-9
- rockylinux-10
- debian-10, debian-11, debian-12, debian-13
- oracle-7
- opensuse-leap-15, opensuse-leap-15-6
- openeuler-2203, openeuler-2403
Image-builder already supports KubeVirt/QEMU for:
- ubuntu-2204, ubuntu-2404
- rockylinux-8, rockylinux-9
- flatcar
Describe the solution you'd like
Extend image-builder’s KubeVirt/QEMU support to include the missing OSes above so Kubespray can fully reuse the shared path.
If full coverage isn’t feasible, we’d like to align on which subset is acceptable so we can reduce Kubespray’s matrix accordingly.
Describe alternatives you've considered
- Keep Kubespray’s standalone KubeVirt image build/CI and avoid shared path.
This avoids gaps but duplicates effort and increases maintenance for both projects.
- Reduce Kubespray’s KubeVirt OS list to only those already supported by image-builder.
This is possible but would drop several currently supported OSes in Kubespray.
Additional context
This request is motivated by kubespray issue #12383 (reduce maintenance by reusing shared image build path).
We’re happy to contribute if the project is open to expanding KubeVirt/QEMU OS coverage. If maintainers prefer a smaller supported set, we can align and update Kubespray accordingly.
/kind feature
We’d appreciate guidance on whether expanding KubeVirt/QEMU OS coverage is in scope for image-builder. If so, we can help with implementation, if not, we’ll plan for a Kubespray-side CI job instead.
Is your feature request related to a problem? Please describe.
Kubespray currently maintains its own KubeVirt image list https://github.com/kubernetes-sigs/kubespray/blob/master/test-infra/image-builder/roles/kubevirt-images/defaults/main.yml and build flow (see kubespray issue #12383). We’re trying to reuse a shared path in
kubernetes-sigs/image-builderinstead of maintaining a separate CI job and image definitions.Right now, image-builder’s KubeVirt path is tied to QEMU targets and only covers a subset of the OSes Kubespray uses.
Missing OSes from the Kubespray KubeVirt list include:
Image-builder already supports KubeVirt/QEMU for:
Describe the solution you'd like
Extend image-builder’s KubeVirt/QEMU support to include the missing OSes above so Kubespray can fully reuse the shared path.
If full coverage isn’t feasible, we’d like to align on which subset is acceptable so we can reduce Kubespray’s matrix accordingly.
Describe alternatives you've considered
This avoids gaps but duplicates effort and increases maintenance for both projects.
This is possible but would drop several currently supported OSes in Kubespray.
Additional context
This request is motivated by kubespray issue #12383 (reduce maintenance by reusing shared image build path).
We’re happy to contribute if the project is open to expanding KubeVirt/QEMU OS coverage. If maintainers prefer a smaller supported set, we can align and update Kubespray accordingly.
/kind feature