Explain Cloud RDI networking for multiple sources and subscriptions

[ZdravkoDonev-redis]

Cloud RDI networking docs currently show only one source connection. Expand the existing overview to explain shared and separate PrivateLink services, connectivity per workspace and subscription, and customer setup responsibilities.

The diagram shows individual configured sources in each subscription, their shared processor and Redis target, and a source using a public IP address or hostname. Add links from workspace and pipeline setup and retain managed-provider requirements.

Validation: the focused Cloud RDI build passes with CI's Hugo 0.143.1. Internal links, anchors, and desktop/mobile diagram rendering were checked. The full local build is blocked by unrelated missing generated client examples. The staging build is running.

Review notes: existing CIDR overlap wording conflicts across pages and needs network review. The deployed-pipeline count is not confirmed across the legacy and workspace APIs; this change adds no numerical pipeline limit. Cross-region connectivity is excluded.

---

Note

Low Risk
Documentation-only changes to Hugo markdown; no application code, auth, or data handling.

Overview
Expands Cloud RDI networking guidance for pipelines with multiple sources, shared or separate PrivateLink services, and multiple Pro subscriptions.

The Networking overview (networking/_index.md) is rewritten from a short link list into a planning guide: workspace/source/target rules, a Mermaid topology diagram (two subscriptions, shared NLB listeners, separate endpoint services, and a public source), a setup decision table, numbered customer-managed PrivateLink steps, and managed provider notes (Atlas handshake per workspace, Snowflake/Supabase caveats). The detailed AWS PrivateLink reference remains linked for failover and addressing.

Create workspace and Configure source now point readers to that page when they need multiple databases or subscriptions.

^{Reviewed by Cursor Bugbot for commit 8d0b149. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Staging links:
https://redis.io/docs/staging/cloud-rdi-networking-topology/operate/rc/rdi/create-workspace/
https://redis.io/docs/staging/cloud-rdi-networking-topology/operate/rc/rdi/define/
https://redis.io/docs/staging/cloud-rdi-networking-topology/operate/rc/rdi/networking/

[github-actions]

🧠 Redis Memory

Found 7 related items from repository history (2 new this commit):

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• PR — RDSC-6038: Update Redis Cloud RDI documentation for 2.0.0

  Updates the Cloud RDI guides for the RDI 2.0.0 console. The current guides describe one source and the older five-step setup. The updated gu

• PR — RDSC-5962: Document AWS CIDR requirements for Cloud RDI workspaces

  Summary

• PR — RC RDI: GA flow

• PR — DOC-6845: Add MongoDB Atlas Private Link tab to Cloud RDI setup guide

  Documents the two-way handshake flow for connecting a MongoDB Atlas source database to Cloud RDI via Private Link: get the Atlas endpoint se

• Commit — Explain Cloud RDI networking for multiple sources and subscriptions 🆕

  Explain Cloud RDI networking for multiple sources and subscriptions

• PR — Document Cloud RDI workspace capacity planning and pipeline scaling 🆕

  Cloud RDI pipelines share the workspace's network capacity. This change explains how to choose a CIDR before creating the workspace and how

Memory updated at 8d0b149

[andy-stark-redis]

@ZdravkoDonev-redis Approved. Text looks fine but I've added a commit to try to increase the text size on the Mermaid diagram while avoiding the scroll as far as possible. Let me know what you think - I'm happy to go back to the large version of the diagram if you prefer that.