OpenShift 4.22 carries user-defined networks into EVPN-VXLAN fabrics
The new BGP EVPN support gives primary cluster user-defined networks a standards-based path into existing data-center fabrics, with virtualization migrations as the clearest early use case.
OpenShift 4.22 adds Border Gateway Protocol Ethernet VPN support for primary cluster user-defined networks, letting an OpenShift overlay participate in the EVPN control plane used by many data-center fabrics. Red Hat’s release notes describe the capability as a way for a ClusterUserDefinedNetwork to integrate more deeply with the surrounding network rather than stopping at the Kubernetes cluster boundary.
What changed
The design builds on two earlier networking steps: user-defined networks in OpenShift 4.18 and BGP support added in the 4.19 line. OpenShift 4.22 now connects those pieces to an EVPN control plane, while VXLAN carries the data plane. In Red Hat’s engineering explanation, OpenShift advertises MAC and IP reachability through BGP EVPN so selected user-defined networks can extend into a customer-managed EVPN fabric.
That moves the EVPN-VXLAN endpoint closer to workloads. Instead of terminating the overlay only at a top-of-rack or leaf switch, the OpenShift side can participate directly, while external EVPN border routers retain responsibility for reachability to wider internal networks, WAN links and the internet. Red Hat says the implementation supports both MAC-VRF and IP-VRF route advertisement for Layer 2 and Layer 3 user-defined networks.
Who should care
The most immediate audience is platform and network teams moving virtual machines onto OpenShift Virtualization. Red Hat positions EVPN as a way to preserve logical network membership, IP addressing and application dependencies while workloads move, reducing the need to redesign or readdress the network during a migration. The same architecture also matters to multi-tenant platforms that need segmentation to continue beyond the cluster boundary.
This is not a replacement for the data-center fabric. It is an integration point. Operators still need compatible EVPN-VXLAN infrastructure and a coordinated design between the OpenShift and network teams. The value is that both sides can use the same standards-based control plane instead of adding a proprietary gateway between them.
What to evaluate
Teams testing the feature should begin with one primary ClusterUserDefinedNetwork and a bounded workload set, then verify route advertisement, failure convergence, segmentation and access through the EVPN border routers. Virtualization programs should test whether migrated VMs keep the expected Layer 2 or Layer 3 identity and whether existing policy and monitoring still see the intended traffic paths.
The OpenShift 4.22 release notes are the product-level starting point; Red Hat’s linked advanced-networking documentation contains the configuration detail. The engineering post also says the architecture is intended to reach managed OpenShift offerings over time, but that forward-looking direction should not be treated as current managed-service availability.
sources
comments · 0