-
Notifications
You must be signed in to change notification settings - Fork 6.4k
Create 2025-04-28-FDQN-Filtering-Egress-Policies.mdx #22031
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
Conversation
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 SummaryAdded documentation for FQDN Filtering in Gateway Egress Policies, allowing administrators to control egress IPs based on destination FQDN.
Added Files
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 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 |
date: 2025-04-28T11:00:00Z | ||
--- | ||
|
||
Cloudflare One administrators can now control which egress IP is used based on a destination's Fully Qualified Domain Nate (FDQN) within Gateway Egress policies. |
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.
Is it worth including a screenshot of the feature configured?
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.
As powerful as the feature is, its just a selector addition so not much to show off UI wise unfourtunley
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.
Doesn't that make it easier to choose a screenshot then? It makes it crystal clear where the feature exists instead of customers needing to "figure it out" since we have a lot of selectors. Great way to easily help with the distribution and product association problem.
Here's a great example from a recent announcement that is basically just a selector: https://developers.cloudflare.com/changelog/2025-04-09-workers-timing/
src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
Outdated
Show resolved
Hide resolved
src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
Outdated
Show resolved
Hide resolved
src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
Outdated
Show resolved
Hide resolved
…-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com>
…-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com>
…-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com>
Congratulations @Encore-Encore, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cma1mn8e842960clawimxguc5 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Summary
Screenshots (optional)
Documentation checklist