Skip to content

Commit e1674eb

Browse files
committed
update titles for example LB configs
1 parent 0fabb71 commit e1674eb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ The application will default to the Cloudflare settings for the load balancer ho
6363

6464
Review common load balancing configurations for published applications behind Cloudflare Tunnel.
6565

66-
### One tunnel per region
66+
### One app per load balancer
6767

6868
For this example, assume we have a web application that runs on servers in two different data centers. We want to connect the application to Cloudflare so that users can access the application from anywhere in the world. Additionally, we want Cloudflare to load balance between the servers such that if the primary server fails, the secondary server receives all traffic.
6969

@@ -106,9 +106,9 @@ As shown in the diagram, a typical setup includes:
106106

107107
Users can now connect to the application using the load balancer hostname (`app.example.com`). Note that this configuration is only valid for [Active-Passive failover](/load-balancing/load-balancers/common-configurations/#active---passive-failover), since each pool only supports one endpoint per tunnel.
108108

109-
### Multiple apps per tunnel
109+
### Multiple apps per load balancer
110110

111-
The following diagram illustrates how to load balance traffic to two different applications on a private network.
111+
The following diagram illustrates how to steer traffic to two different applications on a private network using a single load balancer.
112112

113113
```mermaid
114114
graph LR

0 commit comments

Comments
 (0)