[Load Balancing] Account Load Balancing updates

src/content/docs/load-balancing/additional-options/load-balancing-china.mdx

@@ -25,5 +25,6 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/load_balancers
 
 Load balancers deployed to the China Network currently have the following limitations:
 
-1. Only cookie-based session affinity is supported.
-2. Private network off-ramps (Tunnel, GRE, IPsec) are not supported.
+- Only cookie-based session affinity is supported.
+- Private network off-ramps (Tunnel, GRE, IPsec) are not supported.
+- Private Network Load Balancing is not available on the China Network.

src/content/docs/load-balancing/load-balancers/dns-records.mdx

@@ -9,7 +9,7 @@ head:
 
 ---
 
-When you [create a load balancer](/load-balancing/load-balancers/create-load-balancer/), Cloudflare automatically creates an LB DNS record for the specified **Hostname**. This functionality allows you to use a hostname with or without an existing DNS record.
+When you [create a load balancer](/load-balancing/load-balancers/create-load-balancer/), Cloudflare automatically creates an LB DNS record for the specified **Hostname**. This functionality allows you to use a hostname with or without an existing DNS record. Private load balancers do not receive an automatic DNS record. Instead, you can configure a hostname using your internal DNS system or by applying a Gateway Firewall override.
 
 ## Supported records
 

src/content/docs/load-balancing/load-balancers/index.mdx

@@ -22,6 +22,12 @@ For an overview of how the Cloudflare Load Balancing solution works, refer to [L
 
 For suggestions, refer to [Common load balancer configurations](/load-balancing/load-balancers/common-configurations/).
 
+## Public vs. Private Load Balancers
+
+Public Load Balancers are designed to handle traffic from the public Internet. When deployed, they automatically receive a hostname, making them immediately accessible. These load balancers can direct traffic to a range of destinations, including public hostnames, public IP addresses, and private IP addresses.
+
+Private Load Balancers, in contrast, are meant for internal use within private networks. They do not automatically receive a hostname, but one can be assigned via Gateway Firewall Policies or through an internal DNS system. Private Load Balancers only accept traffic over a private network on-ramp, such as [Cloudflare WARP](/warp-client/) or [Magic WAN](/magic-wan/). They are capable of forwarding traffic exclusively to private IP addresses.
+
 ## Load balancing and existing DNS records
 
 For details about DNS records, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).

src/content/docs/load-balancing/private-network/index.mdx

@@ -54,3 +54,5 @@ Private Network Load Balancing on-ramps, on the other hand, refer to secure path
 * **Intelligent traffic routing**: Benefit from failover for your private traffic and have the ability to monitor the health of these IP targets directly, rather than load balancing to a tunnel and only monitoring the health of the tunnel itself.
 
 * **Host applications on non-standard ports**: Easily specify and route traffic to applications hosted on private IP addresses using non-standard ports, allowing greater flexibility in service configuration without requiring changes to existing infrastructure.
+
+* **Public and Private Load Balancers**: Public LBs can direct Internet traffic to private IP addresses, supporting all L7 products like WAF and API Shield. Private LBs direct traffic originating from private networks to private IP addresses and require an on-ramp like WARP or Magic WAN.

src/content/docs/load-balancing/understand-basics/load-balancing-components.mdx

@@ -14,10 +14,14 @@ This page provides a simplified overview of the three main components of the Clo
 
 For a hostname (`blog.example.com`) to resolve, the Domain Name System (DNS) must return an IP address, where the website or application is hosted (origin).
 
-When you set up a load balancer, Cloudflare automatically creates an [LB DNS record](/load-balancing/load-balancers/dns-records/) for the specified hostname. This means that, according to a [priority order](/load-balancing/load-balancers/dns-records/#priority-order), instead of simply returning an IP address, the logic you introduced using the Cloudflare Load Balancing solution will be considered.
+When you set up a public load balancer, Cloudflare automatically creates an [LB DNS record](/load-balancing/load-balancers/dns-records/) for the specified hostname. This means that, according to a [priority order](/load-balancing/load-balancers/dns-records/#priority-order), instead of simply returning an IP address, the logic you introduced using the Cloudflare Load Balancing solution will be considered.
 
 Note that you can use the root domain as a Load Balancer hostname. When doing so, make sure you enter the hostname without including the auto-generated dot that typically precedes your zone's name.
 
+:::note
+Private load balancers are not automatically associated with a hostname. Private load balancers are created with either a CGNAT IP address or a custom RFC-1918 IP address.
+:::
+
 <Render file="load-balancing-diagram" />
 
 ## Pools

src/content/partials/load-balancing/dns-load-balancing-limitations.mdx

@@ -11,3 +11,4 @@ In comparison to proxied, layer 7 load balancing, DNS-only load balancing:
 * Increases authoritative queries against Cloudflare, which can potentially cost more for customers with usage-based billing.
 * Does not support [session affinity](/load-balancing/understand-basics/session-affinity/).
 * Geo-locates traffic based on the data center associated with the ECS source address, if available. If not available, geo-locates based on a user's recursive resolver, which can sometimes cause issues with [latency-based steering](/load-balancing/understand-basics/traffic-steering/steering-policies/dynamic-steering/).
+* Does not support [Private Network Load Balancing](/load-balancing/private-network/).

src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx

@@ -11,3 +11,4 @@ In comparison to DNS-only load balancing, layer 7 load balancing:
 * Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
 * Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
 * More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
+* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).

src/content/partials/load-balancing/load-balancer-create.mdx

@@ -9,33 +9,35 @@ To create a load balancer in the dashboard:
 
 2. Select **Create Load Balancer**.
 
-3. On the **Hostname** page:
+3. On the **Load Balancer Setup** page select the type of Load Balancer.
+
+4. On the **Hostname** page:
    * Enter a **Hostname**, which is the DNS name at which the load balancer is available. For more details on record priority, refer to [DNS records for load balancing](/load-balancing/load-balancers/dns-records/).
    * Toggle the orange cloud icon to update the [proxy mode](/load-balancing/understand-basics/proxy-modes/), which affects how traffic is routed and which IP addresses are advertised.
    * If you want [session-based load balancing](/load-balancing/understand-basics/session-affinity/), toggle the **Session Affinity** switch.
 
-4. Select **Next**.
+5. Select **Next**.
 
-5. On the **Add a Pool** page:
+6. On the **Add a Pool** page:
    * Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool).
    * If you are going to set [traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/) to **Off**, re-order the pools in your load balancer to adjust the fallback order.
    * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools).
    * If you choose to set traffic steering to **Random**, you can set [Weights](/load-balancing/understand-basics/traffic-steering/steering-policies/standard-options/#random-steering) (via the API) to your pools to determine the percentage of traffic sent to each pool.
 
-6. Select **Next**.
+7. Select **Next**.
 
-7. On the **Monitors** page:
+8. On the **Monitors** page:
    * Review the monitors attached to your pools.
    * If needed, you can attach an existing monitor or [create a new monitor](/load-balancing/monitors/create-monitor/#create-a-monitor).
 
-8. Select **Next**.
+9. Select **Next**.
 
-9. On the **Traffic Steering** page, choose an option for [Traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/) and select **Next**.
+10. On the **Traffic Steering** page, choose an option for [Traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/) and select **Next**.
 
-10. On the **Custom Rules** page, select an existing rule or [create a new rule](/load-balancing/additional-options/load-balancing-rules/).
+11. On the **Custom Rules** page, select an existing rule or [create a new rule](/load-balancing/additional-options/load-balancing-rules/).
 
-11. Select **Next**.
+12. Select **Next**.
 
-12. On the **Review** page:
+13. On the **Review** page:
     * Review your configuration and make any changes.
     * Choose whether to **Save as Draft** or **Save and Deploy**.

src/content/partials/load-balancing/load-balancer-definition.mdx

@@ -3,4 +3,4 @@
 
 ---
 
-A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.).
+A load balancer distributes traffic among pools according to [pool health](/load-balancing/understand-basics/health-details/) and [traffic steering policies](/load-balancing/understand-basics/traffic-steering/steering-policies/). Each load balancer is identified by its DNS hostname (`lb.example.com`, `dev.example.com`, etc.) or IP address.

src/content/partials/load-balancing/session-affinity-definition.mdx

@@ -6,3 +6,7 @@
 When you enable session affinity, your load balancer directs all requests from a particular end user to a specific endpoint. This continuity preserves information about the user session — such as items in their shopping cart — that might otherwise be lost if requests were spread out among multiple servers.
 
 Session affinity can also help reduce network requests, leading to savings for customers with usage-based billing.
+
+:::note
+Session Affinity is only supported by Public Load Balancers.
+:::