[zhivko-kirishev-redis]

Summary

Documents multiple pipelines in one Redis Cloud Data Integration workspace. The on-prem RDI 2.2.0 multi-pipeline docs are in #4270; this Cloud part is a separate PR so that each is easier to review.

Ticket: RDSC-5780

Changes

• Create workspace (create-workspace.md): new Add pipelines to a workspace section with the steps (Add pipeline at the bottom of the workspace, the Create new pipeline dialog, the new Draft row). It also covers the one-setup-at-a-time rule, what the pipelines of a workspace share (CIDR, PrivateLink connections, Role ARNs, RDI database), and billing. The pipeline table description now covers the Status and Billing columns, and the delete steps mention deleting the workspace together with its last pipeline.
• Create data pipeline (define.md): a Name the pipeline step before Settings, with the naming rules. The quick start and the source setup steps link to it.
• View and edit and FAQ: actions apply to one pipeline, except flushing a target database that several pipelines share. View metrics endpoints gives the metrics paths of a named pipeline and says to add a pipeline label to the scrape job of each pipeline. New questions on choosing between a source and a pipeline, and on pipeline isolation. The billing FAQ says the workspace RPU is charged once per workspace and gives a two-pipeline example.
• Overview, networking, and scaling: the pipelines of a workspace share its network range, VPC endpoints, and RDI database. This fixes the statement that each pipeline has its own RDI database. It also says that RDI spreads pipelines across shards approximately evenly, instead of promising one pipeline per shard.
• CIDR allow list and maintenance windows: the target allow list note refers to the workspace CIDR that all pipelines share, and the maintenance note speaks of pipelines in the plural.
• Screenshots: three images cropped from QA console captures in the style of the existing rdi-2-* images. They show the dialog for the first and second pipeline and a workspace with a running and a draft pipeline. They replace rdi-2-workspace-sources.png, whose Streaming status the console now shows as Running. The Workspace actions screenshot stays as it is on main, because Add pipeline is no longer in that menu.

Before merging

• Multiple pipelines are enabled in the production console. The console gates them behind the enableRdiMultiplePipelines LaunchDarkly flag. These pages are not versioned, so they go live on merge.
• Pipeline name length: the docs give 3 to 20 characters, the limit that RDSC-6270 (in review) sets. Until it merges, RDI core, cloud-ui, and cloud-rdi-infra allow 22 characters. The console also accepts 1 and 2 character names, which RDI rejects later. If RDSC-6270 doesn't reach production first, the docs need 22 again.
• Dialog screenshots: rdi-2-create-pipeline.png and rdi-2-create-second-pipeline.png show the 22-character hint. Replace them once the console shows the RDSC-6270 limit. TODO comments mark them on the pages.
• Target database per pipeline: a separate target database for each pipeline is the intended behavior, and the docs describe it. The workspace table and the database Data Integration tab still show a single workspace-level target database. That is a console bug, which is being fixed.
• Add pipeline location: RDSC-6273 (merged in cloud-ui) moved it from the Workspace actions menu to a row at the bottom of each workspace card, and the steps now describe that. A screenshot of the new row is still needed (TODO in create-workspace.md). The empty-workspace image rdi-workspace-add-pipeline.png, used on four pages, may also be outdated.
• Metrics URLs of named pipelines: for a named pipeline, Connect to Prometheus shows the processor URL of the default pipeline and no collector URLs (RDSC-6220, to do). The collector metrics paths of named pipelines aren't routed yet either (fixed by RDSC-6270). View metrics endpoints describes the intended paths.
• Delete workspace is not blocked by existing pipelines. The docs keep the existing warning to delete the pipelines first.

Validation

• Built the site locally with Hugo: no warnings for the Cloud RDI pages.
• Checked that every link and anchor on the changed pages resolves, and that every referenced image exists. The only report was the pre-existing, client-rendered API reference anchor on the scaling page.
• Checked the facts against cloud-ui, rdi-ui, cloud-rdi-service, and redis-data-integration code. Not checked against the production console.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only updates to Redis Cloud RDI guides; no application or infrastructure code changes.

Overview
Documents running multiple independent Data Integration pipelines in one Redis Cloud RDI workspace, including console flows, shared vs per-pipeline resources, and updated screenshots.

The create workspace guide gains Add pipelines to a workspace (naming rules, Workspace actions > Add pipeline, one draft at a time, shared CIDR/PrivateLink/Role ARNs/RDI database, per-pipeline billing). The workspace list now describes Status, Billing, and Running instead of older Streaming wording.

Create data pipeline, quick start, and setup add a Name the pipeline step before Settings. FAQ adds guidance on source vs pipeline, isolation (except shared-target flush), and RPU math when several pipelines are deployed. Scaling corrects that the RDI database is one per workspace (not per pipeline) and softens shard-per-pipeline guarantees. View/edit and related pages clarify per-pipeline actions, cross-pipeline flush impact, and optional workspace deletion with the last pipeline.

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

[github-actions]

Staging links:
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/create-workspace
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/create-workspace/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/define
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/define/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/faq/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/networking/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/quick-start
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/quick-start/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/scale-pipeline/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/setup/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/rdi/view-edit/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/security/cidr-whitelist/
https://redis.io/docs/staging/RDSC-5780-cloud-multi-pipeline-docs/operate/rc/subscriptions/maintenance/set-maintenance-windows/

[github-actions]

🧠 Redis Memory

Found 7 related items from repository history:

• Commit — RDSC-5780: Document multiple pipelines for RDI 2.2.0

  RDSC-5780: Document multiple pipelines for RDI 2.2.0

• 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 — Explain Cloud RDI networking for multiple sources and subscriptions

  Cloud RDI networking docs currently show only one source connection. Expand the existing overview to explain shared and separate PrivateLink

• 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

• 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

• Commit — RDSC-5780: Add the second-pipeline screenshots to the workspace page

  RDSC-5780: Add the second-pipeline screenshots to the workspace page

• Commit — RDSC-5780: Address the review of the Cloud multi-pipeline docs

  RDSC-5780: Address the review of the Cloud multi-pipeline docs

Memory updated at 505785b

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[nicoweidner]

There are a few spots that should be changed (some because of in-flight PRs), and there are also two more spots that are formulated for a single pipeline:

2. security/cidr-whitelist.md:53: "the RDI pipeline's CIDR" is now the workspace CIDR, which all pipelines share. The target allow list entry covers every pipeline.
3. Low: _index.md:128-130 and subscriptions/maintenance/set-maintenance-windows.md:18 still say "your RDI data pipeline" in the singular.

[nicoweidner]

We're about to change the max length to 20 characters, so the pictures will need an update unfortunately 😬

[zhivko-kirishev-redis]

The console still shows the 22-character hint until RDSC-6270 lands, so these screenshots can't be retaken yet. 505785b marks each dialog screenshot with a TODO for replacement, and the PR description lists it under Before merging. Leaving this thread open until the new screenshots are in.

🤖 Addressed by Claude Code