Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions modules/ROOT/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,6 @@
*** xref:manage:kubernetes/k-manage-resources.adoc[Manage Pod Resources]
*** xref:manage:kubernetes/k-scale-redpanda.adoc[Scale]
*** xref:manage:kubernetes/lifecycle/index.adoc[Cluster Maintenance]
**** xref:manage:kubernetes/k-node-pools.adoc[Node Pools]
**** xref:manage:kubernetes/k-nodewatcher.adoc[]
**** xref:manage:kubernetes/k-decommission-brokers.adoc[Decommission Brokers]
**** xref:manage:kubernetes/tiered-storage/k-recovery-mode.adoc[Recovery Mode]
Expand Down Expand Up @@ -250,7 +249,6 @@
** xref:upgrade:k-rolling-upgrade.adoc[Upgrade Redpanda in Kubernetes]
** xref:upgrade:k-upgrade-operator.adoc[Upgrade the Redpanda Operator]
** xref:upgrade:k-compatibility.adoc[]
** xref:upgrade:k-migrate-node-pools.adoc[]
** xref:upgrade:k-migrate-node-pools-manually.adoc[Migrate Node Pools Manually]
** xref:upgrade:deprecated/index.adoc[Deprecated Features]
** xref:upgrade:iceberg-schema-changes-and-migration-guide.adoc[Iceberg Schema Changes in v25.3]
Expand Down
14 changes: 0 additions & 14 deletions modules/get-started/pages/release-notes/operator.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,20 +14,6 @@ See also:

link:https://github.com/redpanda-data/redpanda-operator/blob/release/v26.1.x/operator/CHANGELOG.md[Changelog^]

=== NodePool CRD (beta)

The Redpanda Operator introduces the NodePool custom resource, which lets you manage groups of Redpanda brokers as independent units within a single cluster. Each NodePool creates its own StatefulSet, giving you fine-grained control over broker placement, resources, and lifecycle.

NodePools enable blue/green node pool migrations: you create a new NodePool on the target Kubernetes node pool, and the operator automatically replicates data and decommissions old brokers with zero downtime. This replaces the manual, broker-by-broker migration process.

[NOTE]
====
The NodePool CRD is in beta. You must enable it with `crds.experimental: true` and the `--enable-v2-nodepools` operator flag.
====

* xref:manage:kubernetes/k-node-pools.adoc[Node Pools] -- Learn how NodePools work and how to enable them.
* xref:upgrade:k-migrate-node-pools.adoc[Migrate Node Pools] -- Step-by-step blue/green migration using the NodePool CRD.
* xref:manage:kubernetes/k-node-pools.adoc#migrate-to-nodepools[Migrate an existing cluster to NodePools] -- Transition from operator-managed replicas to NodePool-managed brokers.

=== Prometheus ServiceMonitor for Console

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -676,7 +676,6 @@ If you have rack awareness enabled, you may want to reassign the remaining broke

include::shared:partial$suggested-reading.adoc[]

- xref:manage:kubernetes/k-node-pools.adoc[Node Pools]

- xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission.adoc[`rpk-redpanda-admin-brokers-decommission`]

Expand Down
Loading
Loading