Skip to content

Conversation

@ncrouch-cflare
Copy link
Contributor

Summary

Adding new load balancing changelog entry

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@github-actions github-actions bot added size/m product:load-balancing Related to Load Balancing product labels Jun 3, 2025
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Jun 3, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Added a new load balancing changelog entry detailing recent updates and improvements.

  • Introduced support for orange-clouded origin resolution in Load Balancers.
  • Updated Load Balancing analytics to improve infrastructure performance.
  • Added zone name to Load Balancing API responses.
  • Improved consistency of Cloudflare Tunnel handling within Load Balancers.

Modified Files

  • src/content/docs/load-balancing/changelog.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Copy link
Contributor

@windsurf-bot windsurf-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file skipped due to size limits:
  • public/__redirects

Comment on lines +15 to +49

**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.

Copy link
Contributor

Choose a reason for hiding this comment

The 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.


**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.
Copy link
Contributor

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:

Suggested change
* Discover the new, centralized Load Balancing interface by navigating to the **Load Balancing** at the account level in the Cloudflare dashboard.
* Discover the new, centralized Load Balancing interface by navigating to the **Load Balancing** section at the account level in the Cloudflare dashboard.

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. */}
Copy link
Contributor

Choose a reason for hiding this comment

The 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:load-balancing Related to Load Balancing product size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants