● Covered by 1 source · 1 reportMedium impact1 neutral
EVPN/VXLAN and OpenPERouter enable KubeVirt VM live migration between clusters
Key points
- KubeVirt v1.6 introduced decentralized live migration.
- Cross-cluster VM migration requires a stretched L2 domain and dedicated network path.
- Traditional network changes for L2 stretching are complex and time-consuming.
- EVPN/VXLAN offers an overlay solution for these networking needs.
- OpenPERouter implements EVPN configuration using Kubernetes CRDs.
KubeVirt VM Migration Challenges
KubeVirt allows virtual machines to run on Kubernetes, and version 1.6 introduced decentralized live migration. However, moving VMs between different Kubernetes clusters presents significant networking hurdles. The primary issue is ensuring the VM retains its IP and MAC address on the destination cluster, which necessitates a stretched Layer 2 domain.
Networking Requirements for Cross-Cluster Migration
Two key network requirements for successful cross-cluster live migration are a stretched L2 domain and a dedicated migration path. A stretched L2 domain ensures the VM maintains its network identity, preventing service disruptions for stateful applications. A dedicated migration path is crucial for transferring gigabytes of memory state without congesting application traffic or introducing unpredictable latency.
Limitations of Traditional Networking
In traditional infrastructure, achieving a stretched L2 domain involves complex and time-consuming processes like configuring new VLANs, switch settings, and potentially new hardware. These changes often require scheduled downtime and extensive coordination. While traditional virtualization platforms address these with proprietary solutions, an open-source equivalent needs to function as a declaratively managed overlay without altering the physical network.
EVPN/VXLAN as a Solution
EVPN/VXLAN provides a solution to these networking challenges by creating an overlay network that can span multiple clusters. This technology allows for the creation of stretched Layer 2 domains and can be configured to provide dedicated paths for migration traffic. It operates as a software-defined overlay, avoiding the complexities of physical network reconfigurations.
Kubernetes-Native EVPN with OpenPERouter
OpenPERouter integrates EVPN capabilities directly into Kubernetes by managing its configuration through Custom Resource Definitions (CRDs). This approach allows for declarative management of EVPN settings, making it a Kubernetes-native solution for enabling cross-cluster KubeVirt VM live migration. It uses CRDs like Underlay for BGP peering and L2VNI for Layer 2 overlay creation.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Reporting from
KubeVirt virtual machines face networking challenges when attempting live migration between Kubernetes clusters, primarily due to the need for a stretched Layer 2 domain and a dedicated migration path. EVPN/VXLAN, managed by OpenPERouter as Kubernetes Custom Resources, provides a solution to these networking requirements, allowing VMs to retain their IP and MAC addresses during migration.