DOC-1261 comparison table for cloud deployments #393
Conversation
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughThe PR updates modules/get-started/pages/cloud-overview.adoc to introduce Bring Your Own Cloud (BYOC) as a distinct deployment option, adds a new three-column comparison table (Serverless, Dedicated, BYOC) with detailed attributes, and reorganizes sections to include BYOC/ BYOVPC/BYOVNet content and signup guidance. It updates feature references (e.g., Kafka Connect availability) and adjusts feature status notes (removing Iceberg from Beta; retaining Remote Read Replicas as Beta). Content is restructured to foreground BYOC, revise networking/governance notes, and update cross-references. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Assessment against linked issues
Assessment against linked issues: Out-of-scope changes
Possibly related PRs
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (6)
modules/get-started/pages/cloud-overview.adoc (6)
6-6: Resolve support/SLA wording inconsistenciesLine 6 claims “24x7 support,” while the comparison table and note later narrow this to “Enterprise support … Monday through Friday, plus immediate escalation for production outages 24/7,” and “Enterprise support with annual contracts” for Serverless. This is confusing.
Recommend clarifying the global statement to reflect monitoring vs. support hours, and align the table/notes with official Support terms.
Proposed neutral edits (adjust as per official Support policy):
-Redpanda Cloud is a complete data streaming platform delivered as a fully-managed service. It provides automated upgrades and patching, data balancing, and 24x7 support while continuously monitoring your clusters and underlying infrastructure to meet strict performance, availability, reliability, and security requirements. +Redpanda Cloud is a complete data streaming platform delivered as a fully-managed service. It provides automated upgrades and patching, data balancing, and 24x7 monitoring while meeting strict performance, availability, reliability, and security requirements. Enterprise Support options vary by cluster type and contract.Optionally tweak the note to make hours explicit and consistent:
-* Enterprise support is staffed by streaming experts around the clock Monday through Friday, plus immediate escalation for production outages 24/7. +* Enterprise Support: staffed 24x5 (Mon–Fri) with 24x7 P1 escalation. Contact Redpanda for plan details.Also applies to: 97-101, 107-108
33-36: Clarify current Serverless provider scope“Redpanda’s cloud (AWS only)” likely reflects the current LA scope. Consider making this time-bound to avoid future confusion.
-| Redpanda's cloud (AWS only) +| Redpanda's cloud (currently AWS only)
47-56: Qualify throughput and partition limits as tier-dependentThese maxima typically vary by tier/region/provider and may change. To avoid hard commitments in an overview table, qualify with “Up to …” and add a note pointing to tiers docs.
-| *Max throughput (write, read)* -| 100 MB/s, 300 MB/s -| 400 MB/s, 800 MB/s -| 2 GB/s, 4 GB/s +| *Max throughput (write, read)* +| Up to 100 MB/s, 300 MB/s +| Up to 400 MB/s, 800 MB/s +| Up to 2 GB/s, 4 GB/s @@ -| *Partitions* -| 5,000 -| 45,600 -| 112,500 +| *Partitions* +| Up to 5,000 +| Up to 45,600 +| Up to 112,500And add a clarifying bullet to the note:
* The partition limit is the number of logical partitions before replication occurs. Redpanda Cloud uses a replication factor of three. +* Throughput and partition limits vary by tier, region, and cloud provider. See the BYOC and Dedicated tiers pages for details.
62-66: Confirm OIDC support for Serverless SSOServerless lists only GitHub/Google. If org-level OIDC SSO is (or will be) supported for Serverless, update this row to avoid under-selling. If not supported by design, consider adding a footnote clarifying “SSO refers to Cloud UI login; Kafka API OIDC is not supported.”
148-150: Add GCP example for object storage for completenessYou cite S3 and Azure Storage but not Google Cloud Storage. Add GCS to keep provider parity.
-... including subnets (subnetworks in GCP), IAM roles, and object storage resources (for example, S3 buckets or Azure Storage accounts). +... including subnets (subnetworks in GCP), IAM roles, and object storage resources (for example, Amazon S3 buckets, Google Cloud Storage buckets, or Azure Storage accounts).
159-160: Verify BYOC marketplace billing options (include Azure?)This mentions direct billing, Google Cloud Marketplace, and AWS Marketplace. If BYOC on Azure supports Azure Marketplace billing, add it here for completeness.
-To start using BYOC, contact https://redpanda.com/try-redpanda?section=enterprise-trial[Redpanda sales^] to request a private offer with possible discounts. You are billed directly or through Google Cloud Marketplace or AWS Marketplace. +To start using BYOC, contact https://redpanda.com/try-redpanda?section=enterprise-trial[Redpanda Sales^] to request a private offer with possible discounts. You are billed directly or through AWS Marketplace, Azure Marketplace, or Google Cloud Marketplace (depending on your cloud and contract).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
modules/get-started/pages/cloud-overview.adoc(4 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#361
File: modules/networking/pages/cloud-security-network.adoc:176-179
Timestamp: 2025-07-21T21:52:17.061Z
Learning: In Redpanda Cloud documentation, BYOVPC and BYOVNet are different product names for different cloud providers: BYOVPC is used for AWS and GCP, while BYOVNet is used for Azure. When documentation sections cover multiple cloud providers, the combined notation "BYOVPC/BYOVNet" is correct and should not be changed to use only one term.
📚 Learning: 2025-07-21T21:52:17.061Z
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#361
File: modules/networking/pages/cloud-security-network.adoc:176-179
Timestamp: 2025-07-21T21:52:17.061Z
Learning: In Redpanda Cloud documentation, BYOVPC and BYOVNet are different product names for different cloud providers: BYOVPC is used for AWS and GCP, while BYOVNet is used for Azure. When documentation sections cover multiple cloud providers, the combined notation "BYOVPC/BYOVNet" is correct and should not be changed to use only one term.
Applied to files:
modules/get-started/pages/cloud-overview.adoc
📚 Learning: 2025-08-07T16:36:45.111Z
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#377
File: modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc:35-71
Timestamp: 2025-08-07T16:36:45.111Z
Learning: In Redpanda Cloud documentation, NAT subnet and firewall rule creation commands for GCP Private Service Connect are producer-side infrastructure steps that only BYOC (Bring Your Own Cloud) customers need to perform, since they manage their own VPC. Dedicated cluster customers don't need these steps because Redpanda manages the infrastructure for them. The ifdef::env-byoc[] guard correctly hides these commands from Dedicated users.
Applied to files:
modules/get-started/pages/cloud-overview.adoc
🔇 Additional comments (7)
modules/get-started/pages/cloud-overview.adoc (7)
151-154: Correct use of BYOVPC/BYOVNet naming across providersThe combined “BYOVPC/BYOVNet” phrasing is correct when covering AWS/GCP (BYOVPC) and Azure (BYOVNet) together. Thanks for keeping this consistent.
161-177: Nice, concise positioning of Serverless vs BYOC/DedicatedThis section cleanly sets expectations and links to tier docs. Looks good.
186-221: BYOC shared-responsibility table reads clear and balancedResponsibilities split make sense (for example, VPC peering/customer, service endpoints/Redpanda). No issues spotted.
222-254: BYOVPC/BYOVNet responsibility split matches product intentGood call-out that IAM and Tiered Storage shift to customer in BYOVPC/BYOVNet, with observability nuance noted. This aligns with past guidance.
256-286: Dedicated responsibility table is consistent with managed modelAssignments look correct. No changes requested.
295-296: Kafka Connect note aligns with comparison table“Disabled by default” and “BYOC/Dedicated via Support” matches the table’s “✓ (disabled by default)” entries. Good cross-consistency.
346-350: Beta features list change: confirm cross-doc consistencyRemote Read Replicas are listed here as beta (and removed from any “not supported” mentions). Ensure any other pages that previously flagged RRR as unsupported are updated, and that ICEBERG references were intentionally removed from beta here.
| | *Service-level agreement (SLA)* | ||
| | 99.9% | ||
| | 99.99% | ||
| | 99.99% | ||
|
|
There was a problem hiding this comment.
dedicated/byoc are "up to" 99.99% availability, it depends on if they pick multi-az or not. single-az is 99.5%.
I'm not sure how to best convey this (maybe linking to our SLA doc for authoritative SLAs?)
| | Up to 400 MB/s, 800 MB/s | ||
| | Up to 2 GB/s, 4 GB/s | ||
|
|
||
| | *Partitions* |
There was a problem hiding this comment.
I know we've debated elsewhere about whether this should be called out as logical partitions, or partitions before replication. Shoudl we do similar here?
There was a problem hiding this comment.
Correct, and it's in the list of Notes under this table. But since it was unclear to you when you eyeballed this, I'll update the row in the table to say Partitions, pre-replication
| | 99.99% | ||
| | 99.99% | ||
|
|
||
| | *Max throughput (write, read)* |
There was a problem hiding this comment.
do we need to mention flex tiers somehow? This sort of changes the mechanics of the high end on tiers (or we can wait and revisit once flex tiers are officially released)
|
|
||
| | *Kafka Connect* | ||
| | ✗ | ||
| | ✓ (disabled by default) |
There was a problem hiding this comment.
This is ok as is, but we could also add an asterisk, add a reference after the table, and explain to users how to enable it (a link is good enough)
Co-authored-by: Paulo Borges <paulohtb6@gmail.com>
Description
This pull request updates the comparison table to the Redpanda Cloud overview, making it easier to understand the differences between Serverless, BYOC, and Dedicated cluster types. Is also adds manual deserialization of Schema Registry to the SM/Cloud feature compatibility list.
Resolves https://redpandadata.atlassian.net/browse/DOC-1261
Resolves https://redpandadata.atlassian.net/browse/DOC-1574
Review deadline:
Page previews
Cloud Overview/Cluster types
Redpanda Cloud vs Self-Managed feature compatibility
Checks