A load balancer network simplifies the setup when the on-prem system connects to a single PrivateLink. When PrivateLink is used in conjunction with a bridge system it sits directly behind the load balancer. In this scenario, PrivateLink connects to the load balancer, which has a target group with all bridge nodes and the on-prem system connects to a single PrivateLink address. The cloud node lists the load balancer as the output of the PrivateLink with a bridge system as the target group for the load balancer. If the link points from the on-prem node to the cloud, the Hop1 initiatorNetwork connects the bridge to the on-prem system and is set to No ingress. The Hop1 targetNetwork is the load balancer network and connects the on-prem node to the bridge.
Hop 2 sits between the bridge and cloud systems, which are in the your Virtual Private Cloud (VPC) and should have a direct connection. Hop 2 continues to use the standard network interface or CIDR notation networks as before.