From 1ecb011aa43fb3bca39da30ad055fc64b5c4ee61 Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Wed, 3 Sep 2025 10:33:20 +0100 Subject: [PATCH 1/2] Updates navigation for DLS and LB --- .../docs/data-localization/how-to/pages.mdx | 18 ++++--- .../docs/data-localization/how-to/r2.mdx | 14 ++--- .../docs/data-localization/how-to/workers.mdx | 14 +++-- .../load-balancing-rules/create-rules.mdx | 32 +++++------ .../additional-options/spectrum.mdx | 26 +++++---- .../get-started/enable-load-balancing.mdx | 12 +++-- .../pools/cloudflare-pages-origin.mdx | 53 +++++++++++-------- .../load-balancing/private-network/warp.mdx | 14 +++-- .../understand-basics/adaptive-routing.mdx | 12 +++-- 9 files changed, 112 insertions(+), 83 deletions(-) diff --git a/src/content/docs/data-localization/how-to/pages.mdx b/src/content/docs/data-localization/how-to/pages.mdx index ef828a24c51399d..bf19ee960c7a261 100644 --- a/src/content/docs/data-localization/how-to/pages.mdx +++ b/src/content/docs/data-localization/how-to/pages.mdx @@ -5,7 +5,7 @@ sidebar: order: 2 --- -import { TabItem, Tabs } from "~/components"; +import { TabItem, Tabs, DashButton } from "~/components"; In the following sections, we will give you some details about how to configure Pages with Regional Services and Customer Metadata Boundary. @@ -15,13 +15,15 @@ To configure Regional Services for hostnames [proxied](/dns/proxy-status/) throu -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account. -2. Go to the **Workers & Pages** tab. -3. Select your Pages project. -4. Follow these steps to [create a Custom Domain](/pages/configuration/custom-domains/). -5. Go to the **DNS** of the zone you configured the Custom Domain for. -6. From the **Region** dropdown, select the region you would like to use on your domain. -7. Select **Save**. +1. In the Cloudflare dashboard, go to the **Workers & Pages** page. + + + +2. Select your Pages project. +3. Follow these steps to [create a Custom Domain](/pages/configuration/custom-domains/). +4. Go to the **DNS** of the zone you configured the Custom Domain for. +5. From the **Region** dropdown, select the region you would like to use on your domain. +6. Select **Save**. diff --git a/src/content/docs/data-localization/how-to/r2.mdx b/src/content/docs/data-localization/how-to/r2.mdx index c02906c31cd2638..569dd0ab2ab4acd 100644 --- a/src/content/docs/data-localization/how-to/r2.mdx +++ b/src/content/docs/data-localization/how-to/r2.mdx @@ -5,7 +5,7 @@ sidebar: order: 6 --- -import { Details } from "~/components"; +import { Details, DashButton } from "~/components"; In the following sections, we will give you some details about how to configure R2 with Regional Services and Customer Metadata Boundary. @@ -13,11 +13,13 @@ In the following sections, we will give you some details about how to configure To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of requesting objects from a [R2 Bucket](/r2/buckets/) occurs only in-region, follow these steps: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account. -2. Go to the **R2** tab. -3. Follow the steps to [create a Bucket](/r2/buckets/create-buckets/). -4. [Connect a bucket to a custom domain](/r2/buckets/public-buckets/#connect-a-bucket-to-a-custom-domain). -5. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the configured bucket custom domain to create a `regional_hostnames` with a specific region. +1. In the Cloudflare dashboard, go to the **R2** page. + + + +2. Follow the steps to [create a Bucket](/r2/buckets/create-buckets/). +3. [Connect a bucket to a custom domain](/r2/buckets/public-buckets/#connect-a-bucket-to-a-custom-domain). +4. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the configured bucket custom domain to create a `regional_hostnames` with a specific region. Regional Services only applies to the custom domain configured for an R2 Bucket. diff --git a/src/content/docs/data-localization/how-to/workers.mdx b/src/content/docs/data-localization/how-to/workers.mdx index b35388eabac07f5..48e9ce906a91b86 100644 --- a/src/content/docs/data-localization/how-to/workers.mdx +++ b/src/content/docs/data-localization/how-to/workers.mdx @@ -6,17 +6,21 @@ sidebar: --- +import { DashButton } from "~/components"; + In the following sections, we will give you some details about how to configure Workers with Regional Services and Customer Metadata Boundary. ## Regional Services To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of a Workers project occurs only in-region, follow these steps: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account. -2. Go to the **Workers & Pages** tab. -3. Select your Workers project. -4. Follow the steps to [create a custom domain](/workers/configuration/routing/custom-domains/). -5. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the configured Workers Custom Domain to create a `regional_hostnames` with a specific region. +1. In the Cloudflare dashboard, go to the **Workers & Pages** page. + + + +2. Select your Workers project. +3. Follow the steps to [create a custom domain](/workers/configuration/routing/custom-domains/). +4. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the configured Workers Custom Domain to create a `regional_hostnames` with a specific region. ### Caveats diff --git a/src/content/docs/load-balancing/additional-options/load-balancing-rules/create-rules.mdx b/src/content/docs/load-balancing/additional-options/load-balancing-rules/create-rules.mdx index 3141f5570856083..13de61a25fc1c28 100644 --- a/src/content/docs/load-balancing/additional-options/load-balancing-rules/create-rules.mdx +++ b/src/content/docs/load-balancing/additional-options/load-balancing-rules/create-rules.mdx @@ -6,7 +6,7 @@ sidebar: --- -import { Example } from "~/components" +import { Example, DashButton } from "~/components" Create and manage [Load Balancing rules](/load-balancing/additional-options/load-balancing-rules/) in the **Custom Rules** page, which is part of the Create/Edit Load Balancer workflow found in **Traffic** in the dashboard. @@ -20,20 +20,22 @@ Create and manage [Load Balancing rules](/load-balancing/additional-options/load ## Example Workflow -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select an account. -2. Go to **Load Balancing**. -3. Edit an existing load balancer or [create a new load balancer](/load-balancing/load-balancers/create-load-balancer/). -4. From the Load Balancer workflow, select **Custom Rules**. -5. Select **Create Custom Rule**. -6. In the **Field** drop-down list, choose an HTTP property. For more details, refer to [Supported fields](/load-balancing/additional-options/load-balancing-rules/reference/). -7. In the **Operator** drop-down list, choose an operator. For more details, refer to [Operators](/load-balancing/additional-options/load-balancing-rules/reference/#operators-and-grouping-symbols). -8. Enter the value to match. When the field is an ordered list, **Value** is a drop-down list. Otherwise, **Value** is a text input. -9. (Optional) To create a compound expression using logical operators, select **And** or **Or**. -10. For an action, choose **Respond with fixed response** or **Override** and enter additional details. For a full list of actions, refer to [Actions](/load-balancing/additional-options/load-balancing-rules/actions/). -11. (Optional) Select **Add another override**. -12. After you create your rule, select **Save and Deploy** or **Save as Draft**. -13. Select **Next** and review your changes. -14. Select **Save** to confirm. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + + +2. Edit an existing load balancer or [create a new load balancer](/load-balancing/load-balancers/create-load-balancer/). +3. From the Load Balancer workflow, select **Custom Rules**. +4. Select **Create Custom Rule**. +5. In the **Field** drop-down list, choose an HTTP property. For more details, refer to [Supported fields](/load-balancing/additional-options/load-balancing-rules/reference/). +6. In the **Operator** drop-down list, choose an operator. For more details, refer to [Operators](/load-balancing/additional-options/load-balancing-rules/reference/#operators-and-grouping-symbols). +7. Enter the value to match. When the field is an ordered list, **Value** is a drop-down list. Otherwise, **Value** is a text input. +8. (Optional) To create a compound expression using logical operators, select **And** or **Or**. +9. For an action, choose **Respond with fixed response** or **Override** and enter additional details. For a full list of actions, refer to [Actions](/load-balancing/additional-options/load-balancing-rules/actions/). +10. (Optional) Select **Add another override**. +11. After you create your rule, select **Save and Deploy** or **Save as Draft**. +12. Select **Next** and review your changes. +13. Select **Save** to confirm. :::caution[Warning] diff --git a/src/content/docs/load-balancing/additional-options/spectrum.mdx b/src/content/docs/load-balancing/additional-options/spectrum.mdx index 8a8acaf5e490d15..9b98224aae10e6d 100644 --- a/src/content/docs/load-balancing/additional-options/spectrum.mdx +++ b/src/content/docs/load-balancing/additional-options/spectrum.mdx @@ -8,7 +8,7 @@ head: content: Add load balancing to Spectrum applications --- -import { Render } from "~/components"; +import { Render, DashButton } from "~/components"; You can configure [Spectrum](/spectrum/) with Load Balancing to bring resiliency to your TCP or UDP based applications. @@ -22,15 +22,19 @@ The exact settings will vary depending on your use case. Refer to the following ### 1. Configure your load balancer -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account where the Load Balancing add-on is [enabled](/load-balancing/get-started/enable-load-balancing/). +1. In the Cloudflare dashboard, go to the **Load Balancing** page. -2. Go to **Load Balancing** and select **Create load balancer**. + -3. On the **Load Balancer Setup**, select **Public load balancer** +2. Select an account where the Load Balancing add-on is [enabled](/load-balancing/get-started/enable-load-balancing/). -4. Choose the website to which you want to add this load balancer. +3. Go to **Load Balancing** and select **Create load balancer**. -5. On the **Hostname** page, define the settings presented and select **Next**. +4. On the **Load Balancer Setup**, select **Public load balancer** + +5. Choose the website to which you want to add this load balancer. + +6. On the **Hostname** page, define the settings presented and select **Next**. - 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/). :::caution @@ -40,19 +44,19 @@ The exact settings will vary depending on your use case. Refer to the following - Keep the orange cloud icon enabled, meaning the load balancer is proxied. This refers to the [proxy mode](/load-balancing/understand-basics/proxy-modes/) and, with Spectrum, traffic is always proxied. - Keep **Session Affinity** and **Failover across pools** disabled as these features are not supported with Spectrum. -6. On the **Add a Pool** page, define the settings presented and select **Next**. +7. On the **Add a Pool** page, define the settings presented and select **Next**. - Select one or more existing pools or [create a new pool](/load-balancing/pools/create-pool/#create-a-pool) [^1]. - If needed, update the [fallback pool](/load-balancing/understand-basics/health-details/#fallback-pools) [^2]. -7. On the **Monitors** page, define the settings presented and select **Next**. +8. On the **Monitors** page, define the settings presented and select **Next**. - 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. On the **Traffic Steering** page, choose an option for [Traffic steering](/load-balancing/understand-basics/traffic-steering/steering-policies/) and 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**. -9. Keep **Custom Rules** page empty as this feature is not supported with Spectrum. +10. Keep **Custom Rules** page empty as this feature is not supported with Spectrum. -10. On the **Review** page: +11. On the **Review** page: - Review your configuration and make any changes. - If you set traffic steering to **Off**, re-order the pools in your load balancer to adjust the fallback order. diff --git a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx index 1b4e7fa938ad804..00a8872af0396cf 100644 --- a/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx +++ b/src/content/docs/load-balancing/get-started/enable-load-balancing.mdx @@ -10,15 +10,17 @@ description: Learn how to enable load balancing. --- -import { Render } from "~/components" +import { Render, DashButton } from "~/components" Load balancing is an add-on for your account, meaning your account needs a [billing profile](/billing/create-billing-profile/). To enable [Load Balancing](https://dash.cloudflare.com/?to=/:account/:zone/traffic/load-balancing): -1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Load Balancing**. -3. Select **Enable Load Balancing** in the **Status** column. -4. Choose your plan options and confirm payment. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + + +2. Select **Enable Load Balancing** in the **Status** column. +3. Choose your plan options and confirm payment. diff --git a/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx b/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx index 0b051719137de16..4a377290af6a200 100644 --- a/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx +++ b/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx @@ -12,7 +12,7 @@ sidebar: -import { GlossaryTooltip } from "~/components" +import { GlossaryTooltip, DashButton } from "~/components" This tutorial is intended as an introductory example of how you can leverage Cloudflare's global traffic management. @@ -35,16 +35,16 @@ Make sure you: ## Create health monitor - - Although you can create all the components in the **Create Load Balancer** workflow, using the **Manage Monitors** and **Manage Pools** sections separately makes it easier to test and troubleshoot the configurations of each of these components before bringing them together in a load balancer. Monitors define the criteria based on which an endpoint will be considered healthy or not. Start by setting up a monitor as follows. -1. Log in to your Cloudflare account. -2. Go to **Load Balancing**. -3. Select the **Monitors** tab and then **Create monitor**. -4. Give the monitor a descriptive name and confirm the other fields are filled in as the following: +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + + +2. Select the **Monitors** tab and then **Create monitor**. +3. Give the monitor a descriptive name and confirm the other fields are filled in as the following: @@ -56,7 +56,7 @@ Monitors define the criteria based on which an endpoint will be considered healt -5. Under **Advanced health check settings**, keep the default values and enable the **Follow Redirects** option. +4. Under **Advanced health check settings**, keep the default values and enable the **Follow Redirects** option. When you are using a service like Cloudflare Pages, it is possible that requests from the health monitor - as well as the ones from your visitors - are redirected before reaching their destination. Enabling this option prevents the monitor from reporting an unhealthy endpoint when it actually has only been redirected (with a `301` code, for example). @@ -67,7 +67,7 @@ You can name the monitor after the parameters you have defined. For example: `HT This way you can easily remember the criteria a certain monitor is using when you decide to attach it to other endpoints as well. ::: -6. Select **Save** to confirm. +5. Select **Save** to confirm. @@ -84,7 +84,9 @@ The endpoint pointing to [Cloudflare Pages](/pages/) must have **host header** f Failing to add the host header will result in [response code mismatch error](/load-balancing/troubleshooting/common-error-codes/#response-code-mismatch-error) for the monitor, and [Error 1000: DNS points to prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000/) for visitors (if the load balancer is enabled despite the unhealthy monitor status). ::: -1. Go to **Load Balancing**. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + 2. Select the **Pools** tab and then **Create monitor**. @@ -141,11 +143,13 @@ Failing to add the host header will result in [response code mismatch error](/lo ## Check the endpoints health status +Before setting up the load balancer: +1. In the Cloudflare dashboard, go to the **Load Balancing** page. -Before setting up the load balancer: + -1. Go to **Load Balancing** > **Pools** tab. +1. Go to the **Pools** tab. 2. Find the pools you created in the list and check if their status is `Healthy`. You might have to refresh the page. 3. Expand each pool entry to confirm that the health status for endpoints within them is also `Healthy`. @@ -159,35 +163,40 @@ Revise your pools and monitor configurations to confirm they followed the instru After confirming the endpoints and monitors are set up correctly and return the expected health status, create the load balancer: -1. Go to **Load Balancing** > **Create load balancer**. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. -2. On the **Hostname** page, configure the following and select **Next**. + + +2. Select **Create load balancer**. + +3. On the **Hostname** page, configure the following and select **Next**. * Enter a **Hostname**, which is the DNS name at which the load balancer is available. Suggestion: for now, you can just add a temporary hostname such as `lb` (so the complete field value would look like `lb.`). * 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. * Select your preferred option for [session affinity](/load-balancing/understand-basics/session-affinity/) and [adaptive routing](/load-balancing/understand-basics/adaptive-routing/). -3. On the **Add a Pool** page, configure the following and select **Next**. +4. On the **Add a Pool** page, configure the following and select **Next**. * Select the first pool you created previously and select **Add Pool**. * Do the same for the second pool and reorder them if needed. For the purposes of this tutorial, your production website pool would be the first (`primary`) and the Cloudflare Pages pool would be the second (`secondary`). * If needed, update the [**Fallback Pool**](/load-balancing/understand-basics/health-details/#fallback-pools). For the purposes of this tutorial, you can leave this pointing to your secondary pool. -4. On the **Monitors** page, review the monitors attached to your pools and the expected health status, and select **Next**. +5. On the **Monitors** page, review the monitors attached to your pools and the expected health status, and select **Next**. -5. On the **Traffic Steering** page, make sure **Off** is selected. This means the load balancer will follow the order established on the **Add a Pool** section (Step 3 above), achieving an [Active - Passive Failover](/load-balancing/load-balancers/common-configurations/#active---passive-failover) configuration. +6. On the **Traffic Steering** page, make sure **Off** is selected. This means the load balancer will follow the order established on the **Add a Pool** section (Step 3 above), achieving an [Active - Passive Failover](/load-balancing/load-balancers/common-configurations/#active---passive-failover) configuration. -6. For the purposes of this tutorial, leave the [**Custom Rules**](/load-balancing/additional-options/load-balancing-rules/) option empty. +7. For the purposes of this tutorial, leave the [**Custom Rules**](/load-balancing/additional-options/load-balancing-rules/) option empty. -7. On the **Review** page, review your configuration and select **Save as Draft**. +8. On the **Review** page, review your configuration and select **Save as Draft**. A DNS record of the type `LB` will be created under [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) with the hostname you have defined, and a corresponding load balancer will be added to [**Load Balancing**](https://dash.cloudflare.com/?to=/:account/load-balancing) ## Optional - Deploy on a test hostname +If you have used a temporary hostname for your load balancer, follow the steps below to deploy and test it. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. -If you have used a temporary hostname for your load balancer, follow the steps below to deploy and test it. + -1. Go to **Load Balancing**. 2. In the **Load Balancers** list, locate the load balancer you created under a test hostname (such as `lb`) and enable it. 3. On your browser, request the temporary hostname (`lb.example.com`). You should see the website or application hosted at your primary origin server. 4. Go back to the **Manage Load Balancers** list, select to expand the test load balancer, and disable the primary pool. @@ -202,8 +211,6 @@ After you confirm everything is working correctly, make sure you re-enable the p ## Route production traffic to load balancer - - Now that you have set up your load balancer and verified everything is working correctly, you can put the load balancer on a live domain or subdomain: 1. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage). diff --git a/src/content/docs/load-balancing/private-network/warp.mdx b/src/content/docs/load-balancing/private-network/warp.mdx index 135bc74a72d94c2..cb235e7bb75073d 100644 --- a/src/content/docs/load-balancing/private-network/warp.mdx +++ b/src/content/docs/load-balancing/private-network/warp.mdx @@ -55,13 +55,17 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to ## 3. Create an Account Load Balancer with a Private IP -1. Go to **Load Balancing** at the account level and select **Create a Load Balancer**. -2. Select **Private Load Balancer**. -3. On the next step you can choose to associate this load balancer with either: +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + + +2. Select **Create a Load Balancer**. +3. Select **Private Load Balancer**. +4. On the next step you can choose to associate this load balancer with either: - A CGNAT IP from the Cloudflare range or - A custom [RFC1918 address](https://datatracker.ietf.org/doc/html/rfc1918). -4. Add a descriptive name to identify your Load Balancer. -5. Proceed through the setup. +5. Add a descriptive name to identify your Load Balancer. +6. Proceed through the setup. After selecting an IP address and completing the setup, you will be redirected to the Load Balancing dashboard. You can locate your load balancer using the search bar or by filtering for **Private** load balancers. Be sure to note the assigned IP address as it will be required in the following steps. diff --git a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx index 0cc6536c91493f5..deacf6a90e54e2d 100644 --- a/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx +++ b/src/content/docs/load-balancing/understand-basics/adaptive-routing.mdx @@ -6,7 +6,7 @@ sidebar: --- -import { Render } from "~/components" +import { Render, DashButton } from "~/components" Adaptive routing controls features that modify the routing of requests to pools and endpoints in response to dynamic conditions, such as during the interval between active health monitoring requests. @@ -16,7 +16,9 @@ When there are no healthy endpoints in the same pool, failover across pools exte ### Enable failover across pools -1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Select **Load Balancing**. -3. Navigate to your Load Balancers and select **Edit**. -4. From **Adaptive Routing**, enable **Failover across pools**. +1. In the Cloudflare dashboard, go to the **Load Balancing** page. + + + +2. Navigate to your Load Balancers and select **Edit**. +3. From **Adaptive Routing**, enable **Failover across pools**. From 7ab18f3a1e890edca2dcfcf82d8805df9cee9ff0 Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Wed, 3 Sep 2025 10:49:38 +0100 Subject: [PATCH 2/2] Adds missing componenent --- src/content/docs/load-balancing/private-network/warp.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/load-balancing/private-network/warp.mdx b/src/content/docs/load-balancing/private-network/warp.mdx index cb235e7bb75073d..19fd900c9b7e3f5 100644 --- a/src/content/docs/load-balancing/private-network/warp.mdx +++ b/src/content/docs/load-balancing/private-network/warp.mdx @@ -7,6 +7,8 @@ sidebar: --- +import { DashButton } from "~/components" + To use Private Network Load Balancing, you must first set up a Cloudflare Tunnel and a Virtual Local Area Network in the [Cloudflare Zero Trust Dashboard](http://one.dash.cloudflare.com). This guide walks you through all required steps, from setup to optional configurations. ## 1. Create Tunnel and Virtual Network