Repository navigation
docs: add a connectivity section to the 3.x manual - #1150
Merged
Merged
Conversation
|
Warning Review limit reachedNext included review available in 46 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: QUIET Plan: Advanced Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Mirror 4.x's Connectivity section (scylladb#1130) so the 3.x docs answer the same searches: an index mapping each kind of network to what the driver needs, a VPC peering / Transit Gateway / direct connection page in 3.x API terms, and a client routes page stating that 3.x does not support them and pointing to 4.x. The Address resolution section from scylladb#1081 shrinks to a pointer; its heading is unchanged so the anchor survives. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
nikagra
force-pushed
the
connectivity-3x
branch
from
September 25, 2026 13:15
71aca5d to
482a733
Compare
This was referenced Sep 28, 2026
nikagra
marked this pull request as ready for review
September 28, 2026 13:57
dkropachev
approved these changes
Sep 28, 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.
Depends on: nothing (#1155 and #1156 are merged)
Blocks: nothing
People search the 3.x docs for PrivateLink too, and
scylla-3.xhas only #1081's short note. This adds the 4.x Connectivity section (#1130) toscylla-3.x, where 3.x releases ship.scylla-3.11.5.x, the published 3.x version, only fast-forwards from here, so it reaches/scylla-3.11.5.x/on the next fast-forward; this replaces #1145.manual/connectivity/: an index, a VPC peering page in 3.x API terms, and a client routes page saying 3.x does not support them (DRIVER-437), with 4.x ≥ 4.19.0.7 as the pathwithSSL()does no hostname verification,build()does not connect, a wrong local DC fails only on requests,withoutAdvancedShardAwareness()covers NAT and a blocked shard-aware port, and a translator must map each node to its own address:portcompression/*, using the{eval-rst}fence like the other pages on this branchVerified with
make -C docs teston this branch: exit 0, 0 warnings (the base is also 0), and the new anchor and nav entries render. The driver behaviour described was read from the source, not observed on a cluster. Not checked: search indexing.Refs: #1121
Jira: DRIVER-1043
🤖 Generated with Claude Code