add mermaid diagrams

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/index.mdx

@@ -13,6 +13,26 @@ Our lightweight and open-source connector, [`cloudflared`](https://github.com/cl
 
 Cloudflare Tunnel also allows users to deploy additional instances of our connector, `cloudflared`, for availability and failover scenarios. We refer to these unique instances as replicas. Each replica establishes four new connections which serve as additional points of ingress to your origin, should you need them. Each of the replicas will point to the same tunnel. This ensures that your network remains up in the event a single host running `cloudflared` goes down.
 
+```mermaid
+graph LR
+	C{Cloudflare}
+	subgraph E[Private network]
+			cf1["cloudflared replica <br> (Tunnel-1)"]
+			cf2["cloudflared replica <br> (Tunnel-1)"]
+			S1[Application]
+			cf1-->S1
+			cf2-->S1
+	end
+	C -- "Connections x 4 <br>"--> cf1
+	C --> cf1
+	C --> cf1
+	C --> cf1
+	C -- Connections x 4--> cf2
+	C --> cf2
+	C --> cf2
+	C --> cf2
+```
+
 By design, replicas do not offer any level of traffic steering (random, hash, or round-robin). Instead, when a request arrives to Cloudflare, it will be forwarded to the replica that is geographically closest. If that distance calculation is unsuccessful or the connection fails, we will retry others, but there is no guarantee about which connection is chosen.
 
 ### When to use `cloudflared` replicas
@@ -75,9 +95,38 @@ For information about running `cloudflared` in a Kubernetes deployment, refer to
 
 ## Cloudflare Load Balancers
 
-[Cloudflare Load Balancing](/load-balancing/) allows users to proactively steer traffic away from unhealthy origins (or other <GlossaryTooltip term="endpoint" link="/glossary/?term=endpoint">endpoints</GlossaryTooltip>) and intelligently distribute the traffic load based on a multitude of steering algorithms. This process ensures that errors are not served to end users and empowers businesses to tightly couple overall business objectives to their traffic behavior.
-
-In this model, more than one tunnel is required with identical configurations. The DNS record (`UUID.cfargotunnel.com`) for each Cloudflare Tunnel can be used at the origin within the load balancer. You can then define traffic steering policies to determine how traffic should be routed to each tunnel.
+[Cloudflare Load Balancing](/load-balancing/) proactively steers traffic away from unhealthy origins and intelligently distributes the traffic load based on your choice of [steering algorithms](/load-balancing/understand-basics/traffic-steering/). Load balancers can be configured for traffic originating from both the public Internet and from within a private network.
+
+A load balancer setup requires more than one tunnel with identical configurations. Most customers will create one tunnel per data center and one load balancer pool per tunnel.
+
+```mermaid
+graph LR
+		accTitle: Load balancing traffic to applications behind Cloudflare Tunnel
+
+    A[Internet] --> C{Cloudflare <br> Load Balancer}
+    B[WARP clients] --> C
+		M[Magic WAN] --> C
+    C -- Tunnel 1 --> cf1
+    C -- Tunnel 2 --> cf2
+		subgraph F[Data center 2]
+				cf2[cloudflared <br> server]
+				subgraph pool2[Pool 2]
+       		S3[App server]
+        	S4[App server]
+				end
+				cf2-->S3
+				cf2-->S4
+    end
+		subgraph E[Data center 1]
+				cf1[cloudflared <br> server]
+				subgraph pool1[Pool 1]
+        	S1[App server]
+        	S2[App server]
+				end
+				cf1-->S1
+				cf1-->S2
+    end
+```
 
 ### When to use load balancers
 
@@ -86,6 +135,36 @@ In this model, more than one tunnel is required with identical configurations. T
 - To get alerted when a tunnel reaches an inactive state.
 - To distribute traffic more evenly across your Cloudflare Tunnel-accessible origins or endpoints.
 
-### Deploy a load balancer
-
-Refer to the [Load Balancer page](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) for more information.
+### Public load balancer
+The DNS record (`UUID.cfargotunnel.com`) for each Cloudflare Tunnel can be used at the origin within the load balancer. You can then define traffic steering policies to determine how traffic should be routed to each tunnel.
+
+
+
+### Private load balancer
+
+If the server IPs overlap, then use a different virtual network in each tunnel so that Load Balancer can route requests to the correct data center and server.
+
+```mermaid
+graph LR
+    W[WARP clients] --> C{Private load balancer <br> 100.112.0.0}
+    C -- Tunnel 1 --> cf1
+    C -- Tunnel 2 --> cf2
+		subgraph D2[Data center 2]
+			cf2[cloudflared]
+			subgraph F[Pool 2]
+					S3["Endpoint <br> 10.0.0.1 (VNET-2)"]
+					S4["Endpoint <br> 10.0.0.2 (VNET-2)"]
+			end
+			cf2-->S3
+			cf2-->S4
+		end
+		subgraph D1[Data center 1]
+			cf1[cloudflared]
+			subgraph E[Pool 1]
+					S1["Endpoint <br> 10.0.0.1 (VNET-1)"]
+					S2["Endpoint <br> 10.0.0.2 (VNET-1)"]
+			end
+			cf1-->S1
+			cf1-->S2
+		end
+```