Repository navigation
DOC-7188 Add a Redis Cloud SCH support table for PrivateLink and PSC - #4493
Open
andy-stark-redis wants to merge 2 commits into
Open
andy-stark-redis wants to merge 2 commits into
andy-stark-redis wants to merge 2 commits into
Conversation
Replace the PrivateLink/PSC exclusion prose on the SCH page with a table of
connection method against routing mode, and narrow the matching NOTE in the
four client connect pages (redis-py, node-redis, Lettuce, go-redis).
Mirko Ortensi's Slack message (2026-10-15) is the only source: drop the
PrivateLink limitation on standard routing, keep it for the OSS Cluster API
("still some issues"), keep all of it for PSC. Nothing else is confirmed. The
four follow-up questions Andy posted in that thread were unanswered when this
was written, so every other cell keeps its old limitation (the safest reading)
and the PR is where engineers are expected to correct it. The "not available"
cell for PSC with the OSS Cluster API comes from the PSC limitation as
described, not from a source that says PSC lacks the Cluster API.
The client NOTEs told users to set the maintenance endpoint type to none for
PrivateLink. That advice would now switch off pre-handoffs for PrivateLink on
standard routing, so it is kept only for PSC and PrivateLink with the OSS
Cluster API. Lettuce has no OSS Cluster API support, so its note is unchanged
in substance.
Learned: PrivateLink standard routing is the only limitation Mirko lifted; every other cell is an unconfirmed carry-over
Directive: Do not name VPC peering or Transit Gateway in the "all other" row until an engineer confirms them
Gaps: Whether the endpoint type none advice is still needed for PSC and PrivateLink with the OSS Cluster API; whether the change is live (no Redis Cloud release note written); Hugo build not run
Recheck: when the PrivateLink OSS Cluster API issues are fixed or PSC gains pre-handoffs
Ticket: DOC-7188
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Contributor
🧠 Redis MemoryFound 6 related items from repository history (1 new this commit):
Memory updated at d6ce40a |
Contributor
Contributor
Author
|
Thanks @dwdougherty ! |
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
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.
Implements DOC-7188.
What changed
What is confirmed and what isn't
Mirko Ortensi's Slack message (2026-10-15) confirms only that the PrivateLink limitation is dropped for standard routing. Every other cell keeps its old limitation, so please correct anything wrong.
Questions for engineers
Not done
The Hugo build was not run.
🤖 Generated with Claude Code
Note
Low Risk
Docs-only updates; risk is inaccurate guidance if the PrivateLink standard-routing SCH behavior or table cells don’t match the product.
Overview
Redis Cloud SCH is documented with a connection method × routing mode table in
sch.md(PrivateLink, PSC, and everything else; standard routing vs OSS Cluster API), replacing the old blanket PrivateLink/PSC prose and clarifying where pre-handoffs apply.Client connect pages (go-redis, Lettuce, node-redis, redis-py) narrow the “relaxed timeouts only” SCH note to Google Cloud Private Service Connect and to OSS Cluster API with AWS PrivateLink, and stop telling all PrivateLink users to force
EndpointType/maintEndpointType/none—so it matches full SCH on PrivateLink with standard routing.Lettuce geographic failover is treated as generally available: the preview banner is removed from
lettuce/failover.md, and the supported clients table lists Lettuce basic failover as Yes (no Preview).Reviewed by Cursor Bugbot for commit d6ce40a. Bugbot is set up for automated code reviews on this repo. Configure here.