Clarify Stable IP change policy and DNS redirect language - #5056
Merged
Conversation
Rewrite "Changes to Stable IP ranges" to state the actual commitments: once a region's ranges are published Temporal avoids adding to them and has no plans to remove one, and any unforeseen add or remove comes with six months of advance notice. Remove the "Don't depend on DNS resolution behavior" callout from the Stable IPs section. It named High Availability as the *only* case with guaranteed DNS resolution, which is wrong now that Stable IPs is a second case. The accurate version, listing both, already exists in "When Namespace Endpoint DNS resolution is predictable" on the same page and in the Namespaces page callout. Replace "routes to" with "redirects via DNS to" where the docs describe the Namespace Endpoint reaching an active region. The endpoint does not proxy traffic; it is a DNS redirect. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
lukeknep
commented
Aug 6, 2026
lukeknep
commented
Aug 7, 2026
Co-authored-by: Luke Knepper <lukeknepper@gmail.com>
lukeknep
commented
Aug 7, 2026
Duncanma
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
1. Rewrote "Changes to Stable IP ranges"
The old text said Temporal "does not intend to make changes" and would give "ample time" — vague on both the commitment and the notice period. Replaced with the actual policy:
2. Removed a stale DNS callout from the Stable IPs section
Removed the
:::note Don't depend on DNS resolution behaviorcallout since it was out of place and factually stale. Its content already exists elsewhere:docs/cloud/connectivity/ip-addresses.mdx— the "When Namespace Endpoint DNS resolution is predictable"docs/cloud/get-started/namespaces.mdx— the "Do not take dependencies on Temporal Cloud endpoint DNS resolution" callout3. "routes to" → "redirects via DNS to"
The Namespace Endpoint does not proxy or route traffic; it is a DNS redirect. Fixed the two places that implied otherwise:
architecture-patterns.mdx— "always routes to whichever region currently holds the active Namespace"failovers/index.mdx— "re-routes to the active region" (and dropped the now-redundant "DNS" from the sentence after it)🤖 Generated with Claude Code
┆Attachments: EDU-6906 Clarify Stable IP change policy and DNS redirect language