Isovalent has announced the General Availability of Isovalent Networking for Virtualization, with a focus on BGP EVPN/VXLAN integration between Isovalent Private Networks and Cisco Nexus One data center fabrics. The integration allows Kubernetes worker nodes to peer directly with Cisco Nexus leaf switches via BGP, mapping each Isovalent Private Network to a VRF on the Nexus fabric. Host-specific routes (/32 for IPv4, /128 for IPv6) are dynamically advertised and withdrawn as workloads come online or move, eliminating static routes and NAT. VXLAN encapsulation is handled in eBPF in the Linux kernel with no additional agents. Security Group Tags (SGTs) are carried alongside BGP route advertisements, enabling contract-based policy enforcement on NX-OS. The architecture also supports VM-to-Kubernetes migration via KubeVirt, using a Network Bridge for IP continuity during transition and EVPN for seamless cutover once workloads are fully migrated.

8m read timeFrom isovalent.com
Post cover image
Table of contents
Kubernetes Clusters and the data center fabricHow the Integration WorksMultitenancy with Isovalent Private Networks and Nexus OneWhat This Looks Like with Cisco NX-OSThe Migration MachineGet involvedMore resources
4 Impressions