Isovalent Networking for Virtualization addresses the core challenge of VM migrations: network connectivity breaking during platform moves from VMware to OpenShift Virtualization. It combines two components — Isovalent Network Bridge, which keeps application tiers connected across VMware and OpenShift during phased migrations while preserving IP identity, and Isovalent Private Networks, which provides a VPC-style overlay network model with overlapping CIDRs and multi-tenant segmentation inside Kubernetes. Together they enable incremental, tier-by-tier migrations without forced IP renumbering or downtime risk. The solution also integrates Cilium-based network policies and Timescape dashboards for flow visibility and security validation at each migration step.
Table of contents
If you only read one sectionWhy VM migrations stall at the network layerIntroducing Isovalent Networking for VirtualizationIsovalent Network Bridge: keep apps connected while you moveIsovalent Private Networks: a Kubernetes VPC model for VMs and containersHow the two pieces fit together in a migrationWatch the walkthroughSecurity and visibility that stays consistent as workloads moveMigrate without turning networking into a rewrite projectSort: