Distro News

Red Hat ships BGP cloud connector for Azure OpenShift Virtualization

Key Takeaway

The BGP cloud connector enables direct Layer 3 routing between Azure VNets and guest VMs inside OpenShift clusters, eliminating NAT and preserving VM IP addressability in cloud environments.

Summary

Red Hat has released the BGP cloud connector for Microsoft Azure Red Hat OpenShift, enabling direct IP routing between Azure Virtual Networks and guest virtual machines running inside OpenShift Virtualization clusters. Previously, cloud environments forced virtualization teams to redesign networking architectures because providers expose only Layer 3 networks, requiring NodePort Services and Routes that obscured VM IP addresses behind NAT on worker nodes.

The connector, available on Azure Red Hat OpenShift 4.22 and later with service principal authentication, uses Border Gateway Protocol to advertise routes to Azure Route Server, which programs them into effective routes for each network interface in the VNet. Worker nodes act as routers between the VNet and ClusterUserDefinedNetwork overlays, dynamically updating peer relationships as nodes join or leave the cluster. This allows guest VMs to retain their native IP addresses externally, enabling source-IP-based firewall rules, correct Active Directory dynamic DNS assignment, and proper operation of clustered software that depends on consistent IP visibility.

How the BGP cloud connector changes OpenShift Virtualization networking

  • BGP route advertisement: Cluster worker nodes use Border Gateway Protocol to advertise CUDN routes to Azure Route Server, which then programs effective routes for all Azure network interfaces in the VNet.
  • Dynamic peer management: The connector maintains the set of Route Server peers automatically, updating as worker nodes join or leave the cluster without manual reconfiguration.
  • Layer 3 direct routing: Traffic for the CUDN IP range is routed directly to worker nodes rather than passing through NAT, with the receiving worker forwarding to the guest VM's host.
  • ClusterUserDefinedNetwork integration: Guest VMs receive IP addresses from a CUDN overlay that the VNet is configured to route to, preserving addressability from external Azure resources.
  • Service principal authentication requirement: The feature is gated on clusters using service principal authentication rather than other Azure identity mechanisms.

Why it matters

This development matters for enterprises running hybrid cloud workloads because it removes a significant barrier to migrating on-premise VM estates to managed Kubernetes without refactoring. For Linux distribution and virtualization practitioners, it demonstrates how cloud-native platforms can preserve traditional networking semantics, potentially influencing how other distributions approach cloud VM migration. The collaboration also reinforces the deepening Red Hat-Microsoft partnership around enterprise virtualization, with direct implications for administrators evaluating OpenShift against VMware alternatives.

Original reference: www.redhat.com →