[kubevirt-dev] Kubevirt's Macvtap network binding replacement

[Alona Kaplan]

Hi All,

Following the introduction of Kubevirt Network Binding Plugin API [1] and of Macvtap network binding plugin [2], it's now possible to remove Macvtap network binding implementation from Kubevirt core.

We would like to propose replacing Kubevirt's implementation for Macvtap binding with the Macvtap network binding plugin.

The transition will be conducted in two phases across the next two releases:
Phase 1 (v1.2) - Kubevirt will raise a warning when the Macvtap interface is being used [3].

Phase 2 (v1.3) - Macvtap interface API will stop being supported by kubevirt (using the API will lead to no-op).

Similar to the proposed process to deprecate passt [4].

*In both phases running VMs should have no disruption.

Feel free to share your feedback.

[1] https://kubevirt.io/user-guide/virtual_machines/network_binding_plugins

[2] https://kubevirt.io/user-guide/virtual_machines/net_binding_plugins/macvtap

[3] https://github.com/kubevirt/kubevirt/pull/10924

[4] https://github.com/kubevirt/community/pull/249

Thanks,

Alona.

[Edward Haas]

Hello All,

The removal of the macvtap core binding has been completed [5] towards the Kubevirt v1.3 release.

This completes phase 2.

We are considering a phase 3 in which existing running VMs will break upon upgrade, allowing us to remove

all remaining references in the codebase.

We will update about this in the future.

[5] https://github.com/kubevirt/kubevirt/pull/11901

Best Regards,

Edy.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/CAGyGpwM8VAsWvg2HdZa%3DWfPb-OPS-LUHtjsHpymHH%3DstqyxtUw%40mail.gmail.com.