[Feature Request]: Use KubevirtCI with a local customized Kubernetes repository

[iholder101]

Is your feature request related to a problem? Please describe:
I want to bring up a KubevirtCI cluster with a local Kubernetes repository.
If this would be possible, it will allow:

1. Running KubevirtCI with a Kubernetes branch that hadn't been released yet, for example, running with Kubernetes' current master branch.
2. Running KubevirtCI with a customized development version of Kubernetes. In other words, it would allow changing Kubernetes' code and test the changes with Kubevirt before they've been merged or accepted by Kubernetes.

As a bonus, I think that the second use-case above will also be extremely valuable for Kubernetes developers in general, as currently there is no tool that let's you easily bring up a development Kubernetes cluster based of VMs.

Describe the solution you'd like:
Ideally, I picture the following workflow:

1. Clone Kubernetes repository.
2. (optionally) Make code changes to Kubernetes.
3. Use an environment variable to configure running KubevirtCI with a local Kubernetes repo, for example: export USE_LOCAL_KUBERNETES_REPO=/path/to/my/k8s/repo
4. Use make cluster-up && make cluster-sync as usual.

Describe alternatives you've considered:
It's possible to use kind for a development Kubernetes environment, then install Kubevirt on it. However, kind's node is based on containers which bring many limitations compared to VM based nodes.

Additional context:
As written above, this has potential to help Kubernetes developers in general, not only Kubevirt devs.

[iholder101]

/cc @vladikr @dhiller

[vladikr]

hmm... looks like the "local" provider was removed. #1102
It did pretty much what you are asking for.
I used it extensively in the very distant past.

[vladikr]

@iholder101 maybe you want to take a look at the removed code and revive that?

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[iholder101]

/remove-lifecycle stale