I caught a quick but genuinely eye-opening conversation with Marcos Fernandez from Isovalent — now part of Cisco — on the floor at PlatformCon Live Day London 2026, right at the booth showcasing their newest platform capabilities.
EVPN: Consistent Policy from Kubernetes to the Data Center
The headline feature on display was EVPN — Ethernet VPN — extended to deliver consistent policy and connectivity that spans from Kubernetes clusters all the way through to the physical data center network. That is a meaningfully different problem than the one most Kubernetes CNIs solve. Cluster-internal networking has had good answers for years; the gap has always been at the boundary, where a pod’s network identity has to reconcile with a VLAN, a VXLAN, or a Cisco Nexus switch that has no concept of what a Kubernetes namespace even is.
Isovalent’s pitch is that this boundary should not require a separate, hand-maintained mapping layer. EVPN gives platform teams a single consistent policy model that holds whether traffic is staying inside a cluster, crossing to another cluster, or leaving Kubernetes entirely for a traditional data center segment. For multi-tenant platforms running true multi-tenancy — the same problem space I have written about for zero-trust Kubernetes workloads — that consistency is not a nice-to-have. It is what makes the difference between a network policy that actually holds and one that quietly stops applying the moment traffic crosses an infrastructure boundary nobody thought to test.
What This Means Since the Cisco Acquisition
Being part of Cisco changes the addressable surface for this kind of work. EVPN and VXLAN fabrics are deeply Cisco Nexus territory in most enterprise data centers already; Isovalent’s Cilium-based approach to Kubernetes networking now has a credible path to interoperate with that installed base directly, rather than asking network teams to bolt on yet another overlay. Marcos described the team as being deep in conversations with partners and customers working through real-world use cases — which tracks with how genuinely unglamorous but necessary this integration work is. Nobody gets excited about EVPN in a keynote slide, but every platform team running Kubernetes next to a traditional data center has run into exactly the gap it is meant to close.
The stated goal is straightforward: simplify and stabilize the networking layer for Kubernetes. Compared to some of the more speculative agentic-AI pitches on the floor that day, this was refreshingly concrete — a specific, well-scoped networking problem with a specific, testable answer.
Related Reading
- PlatformCon London 2026: The AI Era Runs on Platforms
- Cilium vs Calico 2026
- Zero-Trust Kubernetes Workloads
- Zero-Trust Kubernetes: Service Mesh and OPA
About the Author
I am Luca Berton, AI and Cloud Advisor. I work at the intersection of platform engineering, cloud security, and enterprise AI deployments. Book a consultation.
