-
Notifications
You must be signed in to change notification settings - Fork 10k
Load balancing changelog #22872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load balancing changelog #22872
Changes from all commits
451ff2b
52397f6
c70bc22
3529e81
154ded6
fb16c35
bb37b44
de6eb8c
4993d03
3aba4ce
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| --- | ||
| title: New Account-Level Load Balancing UI and Private Load Balancers | ||
| description: You can now manage all of your load balancers in one place with the new Load Balancing UI. | ||
| date: 2025-06-03 | ||
| --- | ||
|
|
||
| **Now Available: New Account-Level Load Balancing UI and Private Network Load Balancing** | ||
|
|
||
| We're excited to announce a significant enhancement to the Cloudflare Load Balancing experience! We've launched a redesigned user interface, now centralized at the **account level**, and introduced **Private Load Balancers** to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot. | ||
|
|
||
| This update streamlines how you manage load balancers across multiple zones and extends robust traffic management to your private network infrastructure. | ||
|
|
||
|  | ||
|
|
||
|
|
||
| **Key Enhancements:** | ||
|
|
||
| * **Account-Level UI Consolidation:** | ||
|
|
||
| * **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level. | ||
|
|
||
| * **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution. | ||
|
|
||
| * **Private Network Load Balancing:** | ||
|
|
||
| * **Secure Internal Application Access:** Create **Private Load Balancers** to distribute traffic to applications hosted within your private network, ensuring they are not exposed to the public internet. | ||
|
|
||
| * **WARP & Magic WAN Integration:** Effortlessly direct internal traffic from users connected via Cloudflare WARP or through your Magic WAN infrastructure to the appropriate internal endpoint pools. | ||
|
|
||
| * **Enhanced Security for Internal Resources:** Combine reliable Load Balancing with Zero Trust access controls to ensure your internal services are both performant and only accessible by verified users. | ||
|
|
||
|  | ||
|
|
||
| **Learn More & Get Started:** | ||
|
|
||
| * Discover the new, centralized Load Balancing interface by navigating to the **Load Balancing** at the account level in the Cloudflare dashboard. | ||
|
|
||
| * For detailed information and configuration guides, please visit our developer documentation: | ||
|
|
||
| * [Private Network Load Balancing](https://developers.cloudflare.com/load-balancing/private-network/) | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,14 +1,54 @@ | ||
| --- | ||
| pcx_content_type: changelog | ||
| title: Changelog | ||
| release_notes_file_name: | ||
| - load-balancing | ||
| sidebar: | ||
| order: 153 | ||
| --- | ||
|
|
||
| import { ProductReleaseNotes } from "~/components"; | ||
| import { ProductChangelog } from "~/components"; | ||
|
|
||
| {/* <!-- Actual content lives in /src/content/release-notes/waiting-room.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */} | ||
| {/* <!-- Actual content lives in /src/content/changelog/load-balancing/. Update the file there for new entries to appear here. */} | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The comment on line 10 still references YAML files, but the implementation has changed to use the ProductChangelog component. Consider updating the comment to accurately reflect the new content source. |
||
|
|
||
| <ProductReleaseNotes /> | ||
| <ProductChangelog product="load-balancing" /> | ||
|
|
||
| ## 2025-04-15 | ||
|
|
||
| **Introducing Support for Orange-Clouded Origin Resolution** | ||
|
|
||
| Newly created Cloudflare Load Balancers will resolve orange-clouded origin addresses, provided the origins belong to the same account and zone as the Load Balancer. Existing Load Balancers will continue using the current resolution method. If ownership validation fails, the new system falls back to the existing behavior and defaults to a gray-clouded (DNS-only) lookup, typically resolving to anycast addresses. | ||
|
|
||
| ## 2025-03-13 | ||
|
|
||
| **Update to Load Balancing analytics** | ||
|
|
||
| Load Balancing request rates in analytics may decrease for some customers as an improvement is made to our infrastructure. This decrease in Load Balancing analytics does not indicate a decrease in HTTP requests received. | ||
|
|
||
| ## 2025-02-20 | ||
|
|
||
| **Zone name added to Load Balancing API responses** | ||
|
|
||
| Load Balancing API responses for Load Balancers now include a `zone_name` property, which provides the name of the zone in the response data. | ||
|
|
||
| ## 2025-02-10 | ||
|
|
||
| **Fix for Cloudflare Tunnel Consistency** | ||
|
|
||
| Fixes to improve the consistency of Cloudflare Tunnel handling within Cloudflare Load Balancers. These changes ensure more reliable and predictable routing, particularly when tunnels are involved. | ||
|
|
||
| ## 2025-01-24 | ||
|
|
||
| **Update to Cloudflare Tunnel Steering** | ||
|
|
||
| Introduced changes to the resolution of proxied domains that are backed by Cloudflare Tunnels on the same zone. These changes correct how orange-clouded records are steered to Cloudflare Tunnels via Cloudflare Load Balancers. | ||
|
|
||
| ## 2025-01-16 | ||
|
|
||
| **Update to Pool Health Monitoring** | ||
|
|
||
| We made changes to how we resolve and monitor proxied origins to assess pool health. Our analysis indicates no impact to customer configurations or operations. Contact customer support if you notice any unexpected behavior. | ||
|
|
||
|
Comment on lines
+15
to
+49
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All the changelog entries have dates in 2025 (up to April 2025), but the current date is June 2023. These appear to be future dates, which is unusual for a changelog. Please verify if these dates are correct. |
||
| ## 2024-12-20 | ||
|
|
||
| **Load Balancing with the China Network** | ||
|
|
||
| You can now enable load balancers to be deployed to the [China Network](/china-network/). Refer to the [documentation](/load-balancing/additional-options/load-balancing-china/) for more details. | ||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the 'Learn More & Get Started' section, the navigation instruction is missing a word. Consider updating: