DNM - tiers: Update partition limits

[StephanDollberg]

Document the doubled partition limits in v25.1

Description

Resolves https://redpandadata.atlassian.net/browse/DOC-268
Review deadline: Will merge after 25.1 releases ~March 25

Page previews

What's New in Redpanda Cloud
Cloud Overview
BYOC tiers, Dedicated tiers

Checks

• New feature
• Content gap
• Support Follow-up
• Small fix (typos, links, copyedits, etc)

[netlify]

✅ Deploy Preview for rp-cloud ready!

Name	Link
🔨 Latest commit	fc9dc5a
🔍 Latest deploy log	https://app.netlify.com/sites/rp-cloud/deploys/67b7686eb81cf30008f66507
😎 Deploy Preview	https://deploy-preview-200--rp-cloud.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[StephanDollberg]

To be merged once the change is live in cloud.

[micheleRP]

I think we should also note this in the What's New in Redpanda Cloud. Something like:

=== Increased number of supported partitions

The number of partitions (pre-replication) Redpanda Cloud supports for each (xref:reference:tiers/index.adoc[usage tier]) has been doubled. 

[micheleRP]

This may also hit some marketing collateral. I'll check.

[micheleRP]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

[StephanDollberg]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

Yeah that would probably be the most correct thing to do. If the "what's new" page/docs are somehow linked to a version we could specify it under 25.1 also earlier but if not then it's probably good to wait as people might ask otherwise.

[micheleRP]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

Yeah that would probably be the most correct thing to do. If the "what's new" page/docs are somehow linked to a version we could specify it under 25.1 also earlier but if not then it's probably good to wait as people might ask otherwise.

Thank you, @StephanDollberg! I'll move this into Draft, so it doesn't get merged early!

[toddfarmer]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

Just a note on timing - 25.1 will be available for Cloud customers (roughly) concurrent with the Core GA release of 25.1. Upgrades of existing clusters to a new Core major release has historically lagged by ~6-8 weeks.

[micheleRP]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

Just a note on timing - 25.1 will be available for Cloud customers (roughly) concurrent with the Core GA release of 25.1. Upgrades of existing clusters to a new Core major release has historically lagged by ~6-8 weeks.

@toddfarmer But this will be available immediately for new clusters, right? We have this timing gap for existing clusters with new core features, but we document the feature as soon as it's available for new clusters.

[toddfarmer]

@StephanDollberg is it correct that we should wait for 25.1 to roll out to the entire cloud fleet (end of March) before merging this?

Just a note on timing - 25.1 will be available for Cloud customers (roughly) concurrent with the Core GA release of 25.1. Upgrades of existing clusters to a new Core major release has historically lagged by ~6-8 weeks.

@toddfarmer But this will be available immediately for new clusters, right? We have this timing gap for existing clusters with new core features, but we document the feature as soon as it's available for new clusters.

Correct - I just mention it in the context of "roll out to the entire cloud fleet".