Why your KubeVirt VMs can’t move between clusters — and how EVPN fixes it

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Your team has moved VMs to Kubernetes with KubeVirt. The workloads are running. The team is gaining confidence. Then someone asks: can we live-migrate a VM to the other cluster? 

Disaster recovery, cluster upgrades, capacity rebalancing – the reasons pile up fast. And KubeVirt’s answer appears straightforward: decentralized live migration, which landed in v1.6, should handle this. 

But your network team’s answer is more complicated. The VM likely needs to keep its IP and MAC address on the destination cluster. That means a stretched Layer 2 domain between sites. In traditional infrastructure, you’re looking at new VLANs, switch configurations, and possibly even new hardware. A change window. A ticket. Weeks.

“In traditional infrastructure, you’re looking at new VLANs, switch configurations, and possibly even new hardware. A change window. A ticket. Weeks.”

The migration technology isn’t the problem. What gets in the way, more often than not, is the network.

Why the network is the hard part

Cross-cluster live migration has two network requirements that standard Kubernetes networking doesn’t address.

First, a stretched L2 domain. The VM must land on the destination cluster with the same MAC and IP, on the same broadcast domain. Without this, every migration means IP reassignment, DNS updates, and broken connections. Stateful applications — think PostgreSQL clusters using synchronous replication, or message queues with persistent TCP sessions —  can’t tolerate IP changes without manual intervention.

Second, a dedicated migration path. Migration transfers gigabytes of …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/kubevirt-evpn-vm-migration/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.