docs: sweep rpk redpanda admin deprecation for 26.2 (DOC-2121)

modules/deploy/pages/redpanda/kubernetes/k-production-readiness.adoc

@@ -166,7 +166,7 @@ Decommissioning is used to permanently remove a broker from the cluster, such as
 .Input
 [,bash]
 ----
-kubectl exec -n <namespace> <pod-name> -c redpanda -- rpk redpanda admin brokers list -X user=<sasl-username> -X pass=<sasl-password> -X sasl.mechanism=<sasl-mechanism>
+kubectl exec -n <namespace> <pod-name> -c redpanda -- rpk cluster info -b --detailed -X user=<sasl-username> -X pass=<sasl-password> -X sasl.mechanism=<sasl-mechanism>
 ----
 
 .Output
@@ -216,7 +216,7 @@ Check that Redpanda is running the https://github.com/redpanda-data/redpanda/rel
 .Input
 [,bash]
 ----
-kubectl exec -n <namespace> <pod-name> -c redpanda -- rpk redpanda admin brokers list -X user=<sasl-username> -X pass=<sasl-password> -X sasl.mechanism=<sasl-mechanism>
+kubectl exec -n <namespace> <pod-name> -c redpanda -- rpk cluster info -b --detailed -X user=<sasl-username> -X pass=<sasl-password> -X sasl.mechanism=<sasl-mechanism>
 ----
 
 .Output

modules/deploy/pages/redpanda/manual/production/production-readiness.adoc

@@ -538,7 +538,7 @@ Check that no brokers are in a decommissioned state.
 .Input
 [source,bash]
 ---- 
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 
 .Output

modules/get-started/pages/admin-addresses.adoc

@@ -26,7 +26,7 @@ The following table shows which `rpk` commands require the `-X admin.hosts` or `
 | `rpk cluster` (all except `rpk cluster info` and `rpk cluster metadata`)
 | `-X admin.hosts`
 
-| `rpk redpanda admin`
+| `rpk redpanda admin` (deprecated in 26.2, see xref:upgrade:deprecated/index.adoc[Deprecated features])
 | `--hosts`
 |===
 

modules/get-started/pages/release-notes/redpanda.adoc

@@ -33,6 +33,12 @@ Redpanda version 26.2 validates a broader set of non-Java Apache Kafka® clients
 
 See xref:develop:kafka-clients.adoc[Kafka Compatibility] for the full list of validated clients and known exceptions.
 
+== Simplified cluster administration commands: `rpk redpanda admin` deprecated
+
+Cluster administration moves fully under `rpk cluster`: broker decommissioning, recommissioning, logger control, and per-broker configuration and partition listings now live alongside the other cluster commands, and `rpk cluster info -b --detailed` reports broker membership, liveness, and versions. The `rpk redpanda admin` command tree is deprecated and hidden from help output. The old commands still work and print a pointer to their replacements, but they are planned for removal in a future major release.
+
+See xref:upgrade:deprecated/index.adoc[Deprecated Features] for the full command migration table.
+
 == Tiered Storage v2
 
 Tiered Storage is now available in two versions. Tiered Storage v2 (`tiered_v2`) adds full compaction support for topics stored in object storage: compaction runs on the data in object storage rather than on local data only, eventually retains only the latest value for each key across the entire partition, and removes tombstone records after the retention period configured by `delete.retention.ms`. Topics using Tiered Storage v2 can also be converted to and from Cloud Topics.

modules/manage/pages/cluster-maintenance/decommission-brokers.adoc

@@ -185,7 +185,7 @@ To determine the number of cores that are available across the remaining brokers
 
 [,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 
 .Example output
@@ -234,7 +234,7 @@ rpk cluster info \
 +
 [,bash]
 ----
-rpk redpanda admin brokers decommission <broker-id> \
+rpk cluster brokers decommission <broker-id> \
   --hosts <broker-url>:<admin-api-port> \
   --force
 ----
@@ -247,7 +247,7 @@ If you see `Success, broker <broker-id> has been decommissioned!`, the broker is
 +
 [,bash]
 ----
-rpk redpanda admin brokers decommission-status <broker-id> \
+rpk cluster brokers decommission-status <broker-id> \
   -X admin.hosts=<broker-url>:<admin-api-port>
 ----
 +
@@ -268,5 +268,6 @@ If these steps do not allow the decommissioning process to complete, enable `TRA
 
 include::shared:partial$suggested-reading.adoc[]
 
-* xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission.adoc[`rpk-redpanda-admin-brokers-decommission`]
+// TODO(DOC-2121): Add an xref when the 26.2 rpk regen adds the rpk-cluster-brokers-decommission page.
+* `rpk cluster brokers decommission`
 * https://redpanda.com/blog/raft-protocol-reconfiguration-solution[Engineering a more robust Raft group reconfiguration^]

modules/manage/pages/kubernetes/k-decommission-brokers.adoc

@@ -197,7 +197,7 @@ Next, determine the number of cores that are available across the remaining brok
 
 [,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 
 .Example output
@@ -297,7 +297,7 @@ NOTE: When scaling in a cluster, you cannot choose which broker is removed. Redp
 +
 ```bash
 kubectl --namespace <namespace> exec -ti <pod-name> -c <container-name> -- \
-  rpk redpanda admin brokers decommission <broker-id>
+  rpk cluster brokers decommission <broker-id>
 ```
 +
 This message is displayed before the decommission process is complete.
@@ -312,7 +312,7 @@ TIP: If the broker is not running, use the `--force` flag.
 +
 ```bash
 kubectl --namespace <namespace> exec -ti <pod-name> -c <container-name> -- \
-  rpk redpanda admin brokers decommission-status <broker-id>
+  rpk cluster brokers decommission-status <broker-id>
 ```
 +
 The output uses cached cluster health data that is refreshed every 10 seconds. When the completion column for all rows is 100%, the broker is decommissioned.
@@ -737,6 +737,7 @@ 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`]
+// TODO(DOC-2121): Add an xref when the 26.2 rpk regen adds the rpk-cluster-brokers-decommission page.
+- `rpk cluster brokers decommission`
 
 - https://redpanda.com/blog/raft-protocol-reconfiguration-solution[Engineering a more robust Raft group reconfiguration^]

modules/manage/pages/kubernetes/k-node-pools.adoc

@@ -428,7 +428,7 @@ Monitor the decommission progress:
 
 [source,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 
 Wait until only the Redpanda CR-managed brokers remain.

modules/manage/pages/kubernetes/k-nodewatcher.adoc

@@ -176,4 +176,5 @@ kubectl get persistentvolume --namespace <namespace>
 
 After the PVCUnbinder has finished, xref:manage:kubernetes/k-decommission-brokers.adoc[decommission the broker] that was removed from the node. This is necessary to prevent a potential loss of quorum and ensure cluster stability.
 
-NOTE: Make sure to use the `--force` flag when decommissioning the broker with xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission.adoc[`rpk redpanda admin brokers decommission`]. This flag is required when the broker is no longer running.
+// TODO(DOC-2121): Add an xref when the 26.2 rpk regen adds the rpk-cluster-brokers-decommission page.
+NOTE: Make sure to use the `--force` flag when decommissioning the broker with `rpk cluster brokers decommission`. This flag is required when the broker is no longer running.

modules/manage/pages/kubernetes/k-rolling-restart.adoc

@@ -124,7 +124,7 @@ To view additional information about your brokers, run:
 
 ```bash
 kubectl exec <pod-name> --namespace <namespace> -c redpanda -- \
-  rpk redpanda admin brokers list
+  rpk cluster info -b --detailed
 ```
 
 include::shared:partial$suggested-reading.adoc[]

modules/manage/pages/use-admin-api.adoc

@@ -64,11 +64,12 @@ curl \
 rpk::
 +
 --
-For Linux deployments only, run xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission.adoc[`rpk redpanda admin brokers decommission`]:
+// TODO(DOC-2121): Add an xref when the 26.2 rpk regen adds the rpk-cluster-brokers-decommission page.
+For Linux deployments only, run `rpk cluster brokers decommission`:
 
 [,bash]
 ----
-rpk redpanda admin brokers decommission <broker-id>
+rpk cluster brokers decommission <broker-id>
 ----
 --
 ====

modules/manage/partials/gbac-dp.adoc

@@ -417,7 +417,7 @@ rpk cluster config get nested_group_behavior
 +
 [,bash]
 ----
-rpk redpanda admin config log-level set security --level debug
+rpk cluster loggers set security --level debug
 ----
 +
 This helps diagnose incorrect claim paths, missing groups, or token content issues. The debug level reverts automatically after the expiry period (default: 300 seconds).

modules/troubleshoot/partials/cluster-diagnostics.adoc

@@ -155,7 +155,8 @@ After applying these changes, verify the log level by <<view-redpanda-logs, chec
 
 You can override the log levels for individual subsystems, such as `rpc` and `kafka`, for more detailed logging control. Overrides exist for the entire length of the running Redpanda process.
 
-TIP: To temporarily override the log level for individual subsystems, you can use the xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-config-log-level-set.adoc[`rpk redpanda admin config log-level set`] command.
+// TODO(DOC-2121): Add an xref when the 26.2 rpk regen adds the rpk-cluster-loggers-set page.
+TIP: To temporarily override the log level for individual subsystems, you can use the `rpk cluster loggers set` command.
 
 . List all available subsystem loggers:
 +

modules/upgrade/pages/deprecated/index.adoc

@@ -120,6 +120,20 @@ The following `rpk` commands have been modified or have had flag updates.
 |===
 | Deprecated in | Feature  | Details
 
+// This feature is not supported in cloud
+ifndef::env-cloud[]
+| 26.2.1
+| `rpk redpanda admin`
+| The entire `rpk redpanda admin` command tree is deprecated and hidden from help output. The old commands still work and print a pointer to their replacements. Use the following commands instead:
+
+- `rpk redpanda admin brokers decommission` → `rpk cluster brokers decommission`
+- `rpk redpanda admin brokers decommission-status` → `rpk cluster brokers decommission-status`
+- `rpk redpanda admin brokers recommission` → `rpk cluster brokers recommission`
+- `rpk redpanda admin brokers list` → xref:reference:rpk/rpk-cluster/rpk-cluster-info.adoc[`rpk cluster info`] with `-b --detailed --include-decommissioned`
+- `rpk redpanda admin config print` → xref:reference:rpk/rpk-cluster/rpk-cluster-config-list.adoc[`rpk cluster config list`] with `--node-id <ID>`
+- `rpk redpanda admin config log-level set` → `rpk cluster loggers set`
+- `rpk redpanda admin partitions list` → xref:reference:rpk/rpk-cluster/rpk-cluster-partitions-list.adoc[`rpk cluster partitions list`] with `--node-ids <ID>`
+endif::[]
 // This feature is not supported in cloud
 ifndef::env-cloud[]
 | 23.3.1

modules/upgrade/pages/k-migrate-node-pools-manually.adoc

@@ -357,7 +357,7 @@ redpanda-0    2/2     Running     0    11m     10.244.7.3   kind-worker2
 +
 [source,bash]
 ----
-rpk redpanda admin brokers decommission <broker-id>
+rpk cluster brokers decommission <broker-id>
 ----
 +
 The time required depends on the amount of data being migrated from the broker's partitions. If the broker has a large amount of data, this process can take hours. For more details, see xref:manage:kubernetes/k-decommission-brokers.adoc[Decommission Brokers].
@@ -366,7 +366,7 @@ The time required depends on the amount of data being migrated from the broker's
 +
 [source,bash]
 ----
-rpk redpanda admin brokers decommission-status <broker-id>
+rpk cluster brokers decommission-status <broker-id>
 ----
 +
 Wait until you see this message before proceeding:

modules/upgrade/pages/k-migrate-node-pools.adoc

@@ -162,7 +162,7 @@ List the brokers and confirm their current version:
 
 [source,bash]
 ----
-kubectl exec -n <namespace> redpanda-blue-0 -c redpanda -- rpk redpanda admin brokers list
+kubectl exec -n <namespace> redpanda-blue-0 -c redpanda -- rpk cluster info -b --detailed
 ----
 
 .Expected output
@@ -272,7 +272,7 @@ Verify that all 6 brokers are active and confirm the version split:
 
 [source,bash]
 ----
-kubectl exec -n <namespace> redpanda-blue-0 -c redpanda -- rpk redpanda admin brokers list
+kubectl exec -n <namespace> redpanda-blue-0 -c redpanda -- rpk cluster info -b --detailed
 ----
 
 .Expected output
@@ -306,7 +306,7 @@ Monitor the decommission progress:
 
 [source,bash]
 ----
-kubectl exec -n <namespace> redpanda-green-0 -c redpanda -- rpk redpanda admin brokers list
+kubectl exec -n <namespace> redpanda-green-0 -c redpanda -- rpk cluster info -b --detailed
 ----
 
 You will see blue brokers transition from `active` to `draining` as the operator decommissions them:
@@ -383,7 +383,7 @@ Confirm that all brokers are running the target version:
 
 [source,bash]
 ----
-kubectl exec -n <namespace> redpanda-green-0 -c redpanda -- rpk redpanda admin brokers list
+kubectl exec -n <namespace> redpanda-green-0 -c redpanda -- rpk cluster info -b --detailed
 ----
 
 .Expected output

modules/upgrade/pages/k-rolling-upgrade.adoc

@@ -25,11 +25,11 @@ Before you perform a rolling upgrade:
 
 - Find the Redpanda version that you are currently running.
 +
-To find your current version of Redpanda, use xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-list.adoc[`rpk redpanda admin brokers list`]:
+To find your current version of Redpanda, use xref:reference:rpk/rpk-cluster/rpk-cluster-info.adoc[`rpk cluster info`]:
 +
 ```bash
 kubectl exec <pod-name> --namespace <namespace> -c redpanda -- \
-  rpk redpanda admin brokers list
+  rpk cluster info -b --detailed
 ```
 +
 .Expected output:
@@ -281,7 +281,7 @@ redpanda-post-upgrade-ljqpr             0/1     Completed
 +
 ```bash
 kubectl exec <pod-name> --namespace <namespace> -c redpanda -- \
-  rpk redpanda admin brokers list
+  rpk cluster info -b --detailed
 ```
 
 . If you upgraded from operator v25.1.x to v25.2.x or later, check for Console migration warnings:

modules/upgrade/pages/rolling-upgrade.adoc

@@ -35,10 +35,10 @@ Linux::
 --
 [,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 
-For all available flags, see the xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-brokers-list.adoc[`rpk redpanda admin brokers list` command reference].
+For all available flags, see the xref:reference:rpk/rpk-cluster/rpk-cluster-info.adoc[`rpk cluster info` command reference].
 
 --
 Docker::

modules/upgrade/partials/rolling-upgrades/post-upgrade-tasks.adoc

@@ -10,7 +10,7 @@ rpk cluster health
 To view additional information about your brokers, run:
 
 ```bash
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ```
 
 You can also use the link:/api/doc/admin/operation/operation-post_restart_probe[Admin API] to check how much each broker has progressed in recovering its workloads:

modules/upgrade/partials/rolling-upgrades/rolling-restart-intro.adoc

@@ -11,7 +11,7 @@ If you have topics with `replication.factor=1`, and if you have sufficient disk
 +
 [,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 +
 All brokers should show `active` for `MEMBERSHIP` and `true` for `IS-ALIVE`:
@@ -45,7 +45,7 @@ If you have topics with `replication.factor=1`, and if you have sufficient disk
 +
 [,bash]
 ----
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 +
 All brokers should show `active` for `MEMBERSHIP` and `true` for `IS-ALIVE`:

modules/upgrade/partials/rolling-upgrades/upgrade-your-version.adoc

@@ -19,7 +19,7 @@ First, check which versions are available and verify your current version:
 yum list --showduplicates redpanda
 
 # Check current version
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 +
 Install the specific version you want to upgrade to. Replace `<version>` with the desired version:
@@ -39,7 +39,7 @@ First, check which versions are available and verify your current version:
 apt list --all-versions redpanda
 
 # Check current version
-rpk redpanda admin brokers list
+rpk cluster info -b --detailed
 ----
 +
 Install the specific version you want to upgrade to. Replace `<version>` with the desired version (for example, `25.1.7-1`):