Currently, the passt binary is built as part of kubevirt cluster-sync, with custom kubevirt code, but is not wrapped to a container image.

It is also released on stable releases (about nightlies it is built, but i am not sure it is copied to the cloud artifacts) as binary.

We would need to implement code which wrap the binary in an image (using custom kubevirt code as part of cluster-sync), push it to the registry, so the developer can test upstream custom code easily.

The developer can deploy a DaemonSet with that image, which deploys the binary to the nodes.

The suggested method is to do it as part of kubevirt itself, next to the source code,

by adding BAZEL targets, and pushing it to the registry as done for the Passt SideCar.

Note: even if we do it this way, once there will be merged changes, the only time that it will consume them upstream (i.e on ipam-ext and OVN repos) is when a stable release is out,

we might want to think about this issue as well, but later on.

On D/S we already take kubevirt latest and build there the binary and the container image so we are good.

On U/S we use tagged / stable only, not nightlies which make sense, because it is deterministic reproducible and safer.