From a11ea6bce78feef36cdf4de4b5c4618e06cd97ba Mon Sep 17 00:00:00 2001 From: micheleRP Date: Tue, 19 May 2026 14:25:54 -0600 Subject: [PATCH 01/12] DOC-2202: Document Serverless maintenance behavior Add a Serverless maintenance section to the Upgrades and Maintenance page covering multi-tenant operation, the lack of configurable maintenance windows, and the typical upgrade cadence. Cross-reference the new section from the Serverless cluster type page so customers and Support can find an authoritative answer. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../pages/cluster-types/serverless.adoc | 14 ++++++++- modules/manage/pages/maintenance.adoc | 29 ++++++++++++++++++- 2 files changed, 41 insertions(+), 2 deletions(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 2ecf27d27..53e46280d 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -102,7 +102,19 @@ Not all features included in BYOC clusters are available in Serverless. For exam * Multiple availability zones (AZs) * Role-based access control (RBAC) in the data plane and mTLS authentication for Kafka API clients * Group-based access control (GBAC) -* Kafka Connect +* Kafka Connect +* Configurable maintenance windows. See <>. + +[[maintenance-and-upgrades]] +== Maintenance and upgrades + +Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. + +Maintenance operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. + +If you need control over when maintenance runs on your cluster, use a Dedicated or BYOC cluster, both of which support configurable maintenance windows. + +For the full upgrade and maintenance policy, including the typical cadence for Serverless, see xref:manage:maintenance.adoc[]. == Next steps diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index 4a44222d6..fae7a0b7c 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -5,16 +5,43 @@ As a fully-managed service, the Redpanda Cloud glossterm:control plane[] handles For BYOC and Dedicated deployments, Redpanda manages all maintenance operations for the underlying infrastructure and Kubernetes, ensuring high availability. This includes Kubernetes version upgrades (both the Kubernetes control plane and worker nodes), security patches, and VM image updates. You do not need to act on Kubernetes end-of-life or deprecation notices from your cloud provider (for example, EKS, GKE, or AKS version warnings). Redpanda handles these upgrades on your behalf, targeting completion before the Kubernetes version reaches end of life. +For Serverless deployments, Redpanda manages all maintenance centrally because Serverless clusters run on shared, multi-tenant infrastructure. You cannot configure a maintenance window or per-cluster schedule for a Serverless cluster. See <>. + Redpanda runs maintenance operations on clusters in a rolling fashion, accompanied by a series of health checks, so there is no disruption to the availability of your service. As part of the Kafka protocol, recycling nodes triggers client connections to be restarted. All mainstream client libraries support automatic reconnections when a restart occurs. == Maintenance windows -Redpanda Cloud may run maintenance operations on any day, at any time. You can override this default and schedule a specific maintenance window on your cluster's *Dataplane settings* page. +Maintenance windows are available for BYOC and Dedicated clusters. Serverless clusters do not support configurable maintenance windows; see <>. + +For BYOC and Dedicated clusters, Redpanda Cloud may run maintenance operations on any day, at any time. You can override this default and schedule a specific maintenance window on your cluster's *Dataplane settings* page. If you select a *Scheduled* maintenance window, then Redpanda Cloud runs operations on the day and time specified. Maintenance windows typically take six hours. All operations begin during your maintenance window, but some operations may complete after the window closes. All times are in Coordinated Universal Time (UTC). TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters scheduled for maintenance on Tuesdays are updated first, and clusters scheduled on Mondays are updated last. Keep this in mind when sequencing updates for multiple clusters. +[[serverless-maintenance]] +== Serverless maintenance + +Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to be transparent to your workload. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. + +Typical maintenance cadence for Serverless clusters: + +* *Cloud services*, such as the Cloud UI and control plane: upgraded weekly. +* *Redpanda version upgrades*: approximately three times per year. +* *Infrastructure updates*, including Kubernetes: two to three times per year, as needed. + +These cadences are typical and may change as the service evolves. + +If you need control over when maintenance runs on your cluster, use a xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Dedicated] or xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster. Both support configurable maintenance windows. + +[TIP] +==== +If your Kafka clients are sensitive to brief broker reconnections during rolling operations, consider lowering the metadata refresh interval so clients detect structural changes faster. For example, for librdkafka-based clients: + +* `topic.metadata.refresh.interval.ms=60000` +* `metadata.max.age.ms=240000` +==== + == Minor upgrades During your defined maintenance window, Redpanda Cloud runs minor upgrades. Minor upgrades include standard Redpanda state changes that clients handle gracefully, such as leader elections. From 8a81c4251085ed0c3a1d91a877da8a4a8d18fc8d Mon Sep 17 00:00:00 2001 From: micheleRP Date: Tue, 19 May 2026 14:38:53 -0600 Subject: [PATCH 02/12] edits --- .../get-started/pages/cluster-types/serverless.adoc | 6 ++---- modules/manage/pages/maintenance.adoc | 10 +--------- 2 files changed, 3 insertions(+), 13 deletions(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 53e46280d..3fe1ea13c 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -108,13 +108,11 @@ Not all features included in BYOC clusters are available in Serverless. For exam [[maintenance-and-upgrades]] == Maintenance and upgrades -Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. - -Maintenance operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. +Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. Maintenance operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. If you need control over when maintenance runs on your cluster, use a Dedicated or BYOC cluster, both of which support configurable maintenance windows. -For the full upgrade and maintenance policy, including the typical cadence for Serverless, see xref:manage:maintenance.adoc[]. +For more information, see xref:manage:maintenance.adoc[]. == Next steps diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index fae7a0b7c..b48f6ef42 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -20,7 +20,7 @@ If you select a *Scheduled* maintenance window, then Redpanda Cloud runs operati TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters scheduled for maintenance on Tuesdays are updated first, and clusters scheduled on Mondays are updated last. Keep this in mind when sequencing updates for multiple clusters. [[serverless-maintenance]] -== Serverless maintenance +=== Serverless maintenance Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to be transparent to your workload. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. @@ -34,14 +34,6 @@ These cadences are typical and may change as the service evolves. If you need control over when maintenance runs on your cluster, use a xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Dedicated] or xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster. Both support configurable maintenance windows. -[TIP] -==== -If your Kafka clients are sensitive to brief broker reconnections during rolling operations, consider lowering the metadata refresh interval so clients detect structural changes faster. For example, for librdkafka-based clients: - -* `topic.metadata.refresh.interval.ms=60000` -* `metadata.max.age.ms=240000` -==== - == Minor upgrades During your defined maintenance window, Redpanda Cloud runs minor upgrades. Minor upgrades include standard Redpanda state changes that clients handle gracefully, such as leader elections. From 3bf17bab434f62bb8b32ff7823670852765f9998 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Tue, 19 May 2026 14:44:13 -0600 Subject: [PATCH 03/12] Add page metadata and learning objectives Add :page-topic-type:, :personas:, and :learning-objective-N: attributes to the Upgrades and Maintenance and Serverless pages, plus the checkbox display block, so both pages conform to the docs-team-standards content architecture guide. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../pages/cluster-types/serverless.adoc | 17 ++++++++++++++--- modules/manage/pages/maintenance.adoc | 11 +++++++++++ 2 files changed, 25 insertions(+), 3 deletions(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 3fe1ea13c..efa21e4a6 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -1,16 +1,27 @@ = Serverless :description: Learn how to create a Serverless cluster and start streaming. -:page-aliases: get-started:cluster-types/serverless-pro.adoc, ROOT:deploy:deployment-option/cloud/serverless.adoc +:page-aliases: get-started:cluster-types/serverless-pro.adoc, ROOT:deploy:deployment-option/cloud/serverless.adoc +:page-topic-type: overview +:personas: evaluator, app_developer, platform_admin +:learning-objective-1: Identify the use cases and usage limits for Serverless clusters +:learning-objective-2: Describe how to create a Serverless cluster and connect a client +:learning-objective-3: Recognize which features are supported and unsupported on Serverless -Serverless is the fastest and easiest way to start data streaming. With Serverless clusters, you host your data in Redpanda's VPC, and Redpanda handles automatic scaling, provisioning, operations, and maintenance. This is a production-ready deployment option with a cluster available instantly, and you only pay for what you consume. You can view detailed billing activity for each cluster and edit payment methods on the *Billing* page. +Serverless is the fastest and easiest way to start data streaming. With Serverless clusters, you host your data in Redpanda's VPC, and Redpanda handles automatic scaling, provisioning, operations, and maintenance. This is a production-ready deployment option with a cluster available instantly, and you only pay for what you consume. You can view detailed billing activity for each cluster and edit payment methods on the *Billing* page. [NOTE] ==== -Serverless on GCP is currently in a glossterm:beta[] release. +Serverless on GCP is currently in a glossterm:beta[] release. ==== +After reading this page, you will be able to: + +* [ ] {learning-objective-1} +* [ ] {learning-objective-2} +* [ ] {learning-objective-3} + == Serverless usage limits Each Serverless cluster has the following maximum usage limits: diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index b48f6ef42..25ece4f6d 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -1,5 +1,10 @@ = Upgrades and Maintenance :description: Learn how Redpanda Cloud manages maintenance operations. +:page-topic-type: concepts +:personas: platform_admin, app_developer, streaming_developer +:learning-objective-1: Distinguish maintenance behavior for Serverless versus BYOC and Dedicated clusters +:learning-objective-2: Compare minor upgrades, major upgrades, and deprecations and what to expect from each +:learning-objective-3: Explain how scheduled maintenance windows work for BYOC and Dedicated clusters As a fully-managed service, the Redpanda Cloud glossterm:control plane[] handles all maintenance operations, such as upgrades to your software and infrastructure. Here, _control plane_ refers to the Redpanda Cloud managed service that orchestrates cluster operations, not the Kubernetes control plane. @@ -9,6 +14,12 @@ For Serverless deployments, Redpanda manages all maintenance centrally because S Redpanda runs maintenance operations on clusters in a rolling fashion, accompanied by a series of health checks, so there is no disruption to the availability of your service. As part of the Kafka protocol, recycling nodes triggers client connections to be restarted. All mainstream client libraries support automatic reconnections when a restart occurs. +After reading this page, you will be able to: + +* [ ] {learning-objective-1} +* [ ] {learning-objective-2} +* [ ] {learning-objective-3} + == Maintenance windows Maintenance windows are available for BYOC and Dedicated clusters. Serverless clusters do not support configurable maintenance windows; see <>. From aa39e7c760df294821935adbcdede50898d7acb0 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Tue, 19 May 2026 14:51:42 -0600 Subject: [PATCH 04/12] edit --- modules/manage/pages/maintenance.adoc | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index 25ece4f6d..c5eb0b488 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -2,9 +2,9 @@ :description: Learn how Redpanda Cloud manages maintenance operations. :page-topic-type: concepts :personas: platform_admin, app_developer, streaming_developer -:learning-objective-1: Distinguish maintenance behavior for Serverless versus BYOC and Dedicated clusters -:learning-objective-2: Compare minor upgrades, major upgrades, and deprecations and what to expect from each -:learning-objective-3: Explain how scheduled maintenance windows work for BYOC and Dedicated clusters +:learning-objective-1: Compare minor upgrades, major upgrades, and deprecations and what to expect from each +:learning-objective-2: Explain how scheduled maintenance windows work for BYOC and Dedicated clusters +:learning-objective-3: Distinguish maintenance behavior for Serverless versus BYOC and Dedicated clusters As a fully-managed service, the Redpanda Cloud glossterm:control plane[] handles all maintenance operations, such as upgrades to your software and infrastructure. Here, _control plane_ refers to the Redpanda Cloud managed service that orchestrates cluster operations, not the Kubernetes control plane. @@ -35,14 +35,6 @@ TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters schedu Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to be transparent to your workload. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. -Typical maintenance cadence for Serverless clusters: - -* *Cloud services*, such as the Cloud UI and control plane: upgraded weekly. -* *Redpanda version upgrades*: approximately three times per year. -* *Infrastructure updates*, including Kubernetes: two to three times per year, as needed. - -These cadences are typical and may change as the service evolves. - If you need control over when maintenance runs on your cluster, use a xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Dedicated] or xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster. Both support configurable maintenance windows. == Minor upgrades From 31cd1c1eb219f80d8e4e07e888195cbadb249bc9 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Tue, 19 May 2026 15:46:54 -0600 Subject: [PATCH 05/12] minor edit --- modules/get-started/pages/cluster-types/serverless.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index efa21e4a6..b23d073ef 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -114,7 +114,7 @@ Not all features included in BYOC clusters are available in Serverless. For exam * Role-based access control (RBAC) in the data plane and mTLS authentication for Kafka API clients * Group-based access control (GBAC) * Kafka Connect -* Configurable maintenance windows. See <>. +* Configurable maintenance windows [[maintenance-and-upgrades]] == Maintenance and upgrades From ec4a629751dc91a8caf0af73642876d8439500ce Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 08:05:39 -0600 Subject: [PATCH 06/12] coderabbit suggestion --- modules/manage/pages/maintenance.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index c5eb0b488..77fea8dba 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -33,7 +33,7 @@ TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters schedu [[serverless-maintenance]] === Serverless maintenance -Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to be transparent to your workload. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. +Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to minimize workload impact. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. If you need control over when maintenance runs on your cluster, use a xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Dedicated] or xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster. Both support configurable maintenance windows. From 03f40526debfbce7682a2ab326eceedc289a9141 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 14:52:20 -0600 Subject: [PATCH 07/12] address review: clarify operations run at any time Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/get-started/pages/cluster-types/serverless.adoc | 2 +- modules/manage/pages/maintenance.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index b23d073ef..d66377fec 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -119,7 +119,7 @@ Not all features included in BYOC clusters are available in Serverless. For exam [[maintenance-and-upgrades]] == Maintenance and upgrades -Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. Maintenance operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. +Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. Redpanda may run maintenance operations on Serverless clusters at any time. Running operations continuously is integral to keeping Serverless clusters up to date and secure. Operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. If you need control over when maintenance runs on your cluster, use a Dedicated or BYOC cluster, both of which support configurable maintenance windows. diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index 77fea8dba..9a5988724 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -33,7 +33,7 @@ TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters schedu [[serverless-maintenance]] === Serverless maintenance -Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Operations run in a rolling fashion across the underlying infrastructure and are designed to minimize workload impact. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. +Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Redpanda may run maintenance operations on Serverless clusters at any time. Operations run in a rolling fashion across the underlying infrastructure and are designed to minimize workload impact. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. If you need control over when maintenance runs on your cluster, use a xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Dedicated] or xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster. Both support configurable maintenance windows. From 10a452f8d5fcfba383b030d5643f947d02ecf896 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 15:51:05 -0600 Subject: [PATCH 08/12] add to list of beta features in overview + move note --- modules/get-started/pages/cloud-overview.adoc | 5 +++-- .../get-started/pages/cluster-types/serverless.adoc | 12 ++++++------ 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/modules/get-started/pages/cloud-overview.adoc b/modules/get-started/pages/cloud-overview.adoc index 95d406dc5..9f336ea67 100644 --- a/modules/get-started/pages/cloud-overview.adoc +++ b/modules/get-started/pages/cloud-overview.adoc @@ -420,7 +420,7 @@ Features in limited availability are production-ready and are covered by Redpand The following features are currently in limited availability in Redpanda Cloud: -* xref:ai-agents:adp-overview.adoc[Redpanda ADP] including AI agents, AI Gateway, and transcripts +* xref:ai-agents:adp-overview.adoc[Redpanda Agentic Data Plane (ADP)] * Dedicated for Azure == Features in beta @@ -429,7 +429,8 @@ Features in beta are available for testing and feedback. They are not covered by The following features are currently in beta in Redpanda Cloud: -* BYOVNet for Azure +* Serverless on GCP +* BYOVNet on Azure * Secrets management for BYOVPC on GCP * Several Redpanda Connect components diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index d66377fec..8ff4fad14 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -10,12 +10,6 @@ Serverless is the fastest and easiest way to start data streaming. With Serverless clusters, you host your data in Redpanda's VPC, and Redpanda handles automatic scaling, provisioning, operations, and maintenance. This is a production-ready deployment option with a cluster available instantly, and you only pay for what you consume. You can view detailed billing activity for each cluster and edit payment methods on the *Billing* page. -[NOTE] -==== -Serverless on GCP is currently in a glossterm:beta[] release. - -==== - After reading this page, you will be able to: * [ ] {learning-objective-1} @@ -54,6 +48,12 @@ Make sure you have the latest version of `rpk`, the Redpanda CLI. See xref:get-s == Get started with Serverless +[NOTE] +==== +Serverless on GCP is currently in a glossterm:beta[] release. + +==== + Choose the option that fits how you want to subscribe: include::get-started:partial$get-started-serverless.adoc[] From ff3f1b04e7571d750672ed39a481a85d0e636783 Mon Sep 17 00:00:00 2001 From: Michele Cyran Date: Wed, 20 May 2026 15:51:24 -0600 Subject: [PATCH 09/12] Update modules/get-started/pages/cluster-types/serverless.adoc Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com> --- modules/get-started/pages/cluster-types/serverless.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 8ff4fad14..23c817556 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -119,7 +119,7 @@ Not all features included in BYOC clusters are available in Serverless. For exam [[maintenance-and-upgrades]] == Maintenance and upgrades -Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. Redpanda may run maintenance operations on Serverless clusters at any time. Running operations continuously is integral to keeping Serverless clusters up to date and secure. Operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. +Redpanda manages all maintenance for Serverless clusters. Because Serverless runs on shared, multi-tenant infrastructure, you cannot configure a maintenance window or schedule upgrades for an individual cluster. Redpanda may run maintenance operations on Serverless clusters at any time. Continuous operations are integral to keeping Serverless clusters up to date and secure. Operations run in a rolling fashion and are designed to be non-disruptive. Mainstream Kafka client libraries reconnect automatically when broker connections restart. If you need control over when maintenance runs on your cluster, use a Dedicated or BYOC cluster, both of which support configurable maintenance windows. From bbe92cb016212ee8150f222ef341c9594fb921ad Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 16:00:32 -0600 Subject: [PATCH 10/12] incorporate doc review feedback --- modules/manage/pages/maintenance.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc index 9a5988724..9ecffc2a6 100644 --- a/modules/manage/pages/maintenance.adoc +++ b/modules/manage/pages/maintenance.adoc @@ -22,7 +22,7 @@ After reading this page, you will be able to: == Maintenance windows -Maintenance windows are available for BYOC and Dedicated clusters. Serverless clusters do not support configurable maintenance windows; see <>. +Maintenance windows are available for BYOC and Dedicated clusters. For BYOC and Dedicated clusters, Redpanda Cloud may run maintenance operations on any day, at any time. You can override this default and schedule a specific maintenance window on your cluster's *Dataplane settings* page. @@ -31,7 +31,7 @@ If you select a *Scheduled* maintenance window, then Redpanda Cloud runs operati TIP: Redpanda Cloud maintenance cycles always start on Tuesdays. Clusters scheduled for maintenance on Tuesdays are updated first, and clusters scheduled on Mondays are updated last. Keep this in mind when sequencing updates for multiple clusters. [[serverless-maintenance]] -=== Serverless maintenance +== Serverless maintenance Serverless clusters run on shared, multi-tenant infrastructure, so Redpanda manages all maintenance centrally. You cannot configure a maintenance window, choose a maintenance day, or defer upgrades for an individual Serverless cluster. Redpanda may run maintenance operations on Serverless clusters at any time. Operations run in a rolling fashion across the underlying infrastructure and are designed to minimize workload impact. As with BYOC and Dedicated, all mainstream Kafka client libraries support automatic reconnections when a restart occurs. From e02c9b4423b7fe9f352f59984fdc0725da95cdb5 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 16:14:05 -0600 Subject: [PATCH 11/12] split steps for clarify --- modules/get-started/pages/cluster-types/serverless.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 23c817556..736f07ec2 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -68,9 +68,11 @@ To create a Serverless cluster: + If you don't have an existing resource group, you can create one. Refresh the page to see newly-created resource groups. -. Select a cloud provider and xref:reference:tiers/serverless-regions.adoc[region]. For best performance, select the region closest to your applications. Redpanda expects your applications to be deployed in the same cloud provider and region as your Serverless cluster. -+ -Clusters on AWS can enable private access between their VPC and Redpanda, so data does not traverse the public internet. Private connectivity is implemented using AWS PrivateLink for secure traffic. +. Select a cloud provider: AWS or GCP. (GCP is currently in a glossterm:beta[] release.) + +. Select a xref:reference:tiers/serverless-regions.adoc[region]. For best performance, select the region closest to your applications. Redpanda expects your applications to be deployed in the same cloud provider and region as your Serverless cluster. + +. *AWS only*: Clusters on AWS can enable private access between their VPC and Redpanda, so data does not traverse the public internet. Private connectivity is implemented using AWS PrivateLink for secure traffic. + ** When you enable both public access and private access on the cluster, you can choose between the public address or the private address. When the public address is used the data flows over the public internet. ** You can either create a new PrivateLink or use an existing one from the same resource group. From f5148c41f596d43074639ddfd003afab699d20ae Mon Sep 17 00:00:00 2001 From: micheleRP Date: Wed, 20 May 2026 16:21:09 -0600 Subject: [PATCH 12/12] minor edit --- modules/get-started/pages/cluster-types/serverless.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/get-started/pages/cluster-types/serverless.adoc b/modules/get-started/pages/cluster-types/serverless.adoc index 736f07ec2..13f3c4a6f 100644 --- a/modules/get-started/pages/cluster-types/serverless.adoc +++ b/modules/get-started/pages/cluster-types/serverless.adoc @@ -76,7 +76,7 @@ If you don't have an existing resource group, you can create one. Refresh the pa + ** When you enable both public access and private access on the cluster, you can choose between the public address or the private address. When the public address is used the data flows over the public internet. ** You can either create a new PrivateLink or use an existing one from the same resource group. -** You can enable or disable private access at any time on the cluster's *Settings* page. +** You can enable or disable private access at any time on the cluster's *Dataplane settings* page. ** Enabling private access incurs additional charges. + NOTE: After private access is disabled, attempts to reach the private endpoints will fail. However, the PrivateLink endpoint in your AWS account and the PrivateLink resource in Redpanda Cloud both remain provisioned and continue to incur charges until you explicitly delete them.