Goal

Build CNV 4.18.z from a downstream fork of KubeVirt, which has upstream-incompatible backports

User Stories

As CNV Product Manager, I would like to introduce a feature which is not available upstream into CNV 4.16.z, in order to satisfy urgent customer demand.
As a CNV developer I would like to have a downstream git fork of KubeVirt, possibly under the openshift github org, where I can introduce downstream-only PRs into stable branches.
- I would like these PRs to be rebased periodically on top of the upstream content
- When I propose a new PR, I would like to receive an immediate feedback that the PR builds and passes sanely
- When the PRs are rebased, I would like to receive an immediate feedback that the PR builds and passes sanely
- As a container owner, I would like to configure CPaaS to build from the downstream fork if I choose so.

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

relates to

CNV-23297 CNV private builds for developers

1.	upstream roadmap issue	Closed	Unassigned
2.	upstream design	New	Unassigned
3.	upstream documentation	New	Unassigned
4.	upgrade consideration	New	Unassigned
5.	CEE/PX summary presentation	New	Unassigned
6.	test plans in polarion	New	Unassigned
7.	automated tests	New	Unassigned
8.	downstream documentation merged	New	Unassigned