25.1 rpk single source (#1106)

Co-authored-by: Michele Cyran <michele@redpanda.com>

Author: kbatuigas

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-get.adoc

@@ -29,5 +29,4 @@ rpk cluster config get <key> [flags]
 |--profile |string |Profile to use. See xref:reference:rpk/rpk-profile.adoc[`rpk profile`] for more details.
 
 |-v, --verbose |- |Enable verbose logging.
-|===
-
+|===

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-set.adoc

@@ -1,18 +1,32 @@
 = rpk cluster config set
+// tag::single-source[]
 
-Set a single cluster configuration property.
+Set a cluster configuration property. You can set a single property or multiple properties at once, for example:
 
-This command is provided for use in scripts. For interactive editing, or bulk
-changes, use the `edit` and `import` commands respectively.
-
-You may also use `<key>=<value>` notation for setting configuration properties:
+[,bash]
+----
+rpk cluster config set audit_enabled true
+----
 
 [,bash]
 ----
-rpk cluster config set log_retention_ms=-1
+rpk cluster config set iceberg_enabled=true iceberg_catalog_type=rest
 ----
 
-If an empty string is given as the value, the property is reset to its default.
+You must use `<key>=<value>` notation to set multiple properties.
+
+ifndef::env-cloud[]
+If you set the cluster property value to an empty string, the property is reset to its default.
+
+This command is provided for use in scripts. For interactive editing, or bulk
+changes, use the `edit` and `import` commands respectively.
+endif::[]
+
+ifdef::env-cloud[]
+The output returns an operation ID. Use the xref:reference:rpk/rpk-cluster/rpk-cluster-config-status.adoc[`status`] command to check the progress of the configuration change.
+endif::[]
+
+For a list of available properties, see xref:reference:properties/cluster-properties.adoc[].
 
 == Usage
 
@@ -54,3 +68,5 @@ Workaround: Use `--` to disable parsing for all subsequent characters. For examp
 rpk cluster config set -- delete_retention_ms -1
 ```
 ====
+
+// end::single-source[]

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config-status.adoc

@@ -1,15 +1,38 @@
 = rpk cluster config status
+// tag::single-source[]
 
-Get configuration status of redpanda nodes.
+ifndef::env-cloud[]
+Get the configuration status of Redpanda brokers.
 
-For each node, indicate whether a restart is required for settings to
-take effect, and any settings that the node has identified as invalid
-or unknown properties.
+For each broker, the command output shows:
 
-Additionally show the version of cluster configuration that each node
-has applied: under normal circumstances these should all be equal,
-a lower number shows that a node is out of sync, perhaps because it
-is offline.
+- Whether you need to restart the broker to apply the new settings
+- Any settings that the broker has flagged as invalid or unknown
+
+The command also returns the version of cluster configuration that each broker
+has applied. The version should be the same across all brokers, and
+it is incremented each time a configuration change is applied to the
+cluster. If a broker is using an earlier version as indicated by a lower number,
+it may be out of sync with the rest of the cluster. This can happen if a broker
+is offline or if it has not yet applied the latest configuration changes.  The cluster configuration version number is not the same as the Redpanda version number.
+endif::[]
+
+ifdef::env-cloud[]
+Check the progress of a cluster configuration change.
+
+Some cluster properties require a rolling restart when updated, and it can take several minutes for the update to complete. This command lists the long-running operations run by the update and their status:
+
+- In progress (running)
+- Completed
+- Failed
+
+[,bash,role=no-copy]
+----
+OPERATION-ID          STATUS   STARTED              COMPLETED
+d0ec1obmpnr7lv17bfpg  RUNNING  2025-05-08 14:34:09
+d0ec0sor49uba166af3g  RUNNING  2025-05-08 14:32:20
+----
+endif::[]
 
 == Usage
 
@@ -37,3 +60,4 @@ rpk cluster config status [flags]
 |-v, --verbose |- |Enable verbose logging.
 |===
 
+// end::single-source[]

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-config.adoc

@@ -1,24 +1,32 @@
 = rpk cluster config
+// tag::single-source[]
 
 Interact with cluster configuration properties.
 
-Cluster properties are redpanda settings which apply to all nodes in
-the cluster. These are separate to node properties, which are set with
+ifdef::env-cloud[]
+Cluster properties are Redpanda settings that apply to all brokers in
+the cluster.
+endif::[]
+
+ifndef::env-cloud[]
+Cluster properties are Redpanda settings that apply to all brokers in
+the cluster. These are separate from broker properties, which apply to only that broker and are set with
 `rpk redpanda config`.
 
 Use the `edit` subcommand to interactively modify the cluster configuration, or
-`export` and `import` to write configuration to a file that can be edited and
+`export` and `import` to write the configuration to a file that can be edited and
 read back later.
 
-These commands take an optional `--all` flag to include all properties including
-low level tunables such as internal buffer sizes, that do not usually need
+These commands take an optional `--all` flag to include all properties such as
+low-level tunables (for example, internal buffer sizes) that do not usually need
 to be changed during normal operations. These properties generally require
-some expertize to set safely, so if in doubt, avoid using `--all`.
+some expertise to set safely, so if in doubt, avoid using `--all`.
+endif::[]
 
-Modified properties are propagated immediately to all nodes. The `status`
-subcommand can be used to verify that all nodes are up to date, and identify
-any settings which were rejected by a node, for example if a node is running a
-different redpanda version that does not recognize certain properties.
+Modified properties are propagated immediately to all brokers. Use the `status`
+subcommand to verify that all brokers are up to date and identify
+any settings which were rejected by a broker; for example, if the broker is running a
+different Redpanda version that does not recognize certain properties.
 
 == Usage
 
@@ -46,3 +54,4 @@ rpk cluster config [command]
 |-v, --verbose |- |Enable verbose logging.
 |===
 
+// end::single-source[]

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-cancel-mount.adoc

@@ -1,6 +1,11 @@
 = rpk cluster storage cancel mount
 // tag::single-source[]
 
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
 Cancels a mount/unmount operation on a topic.
 
 Use the migration ID that is emitted when the mount or unmount operation is executed. You can also get the migration ID by listing the mount/unmount operations.

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-list-mount.adoc

@@ -1,7 +1,12 @@
 = rpk cluster storage list mount
 // tag::single-source[]
 
-List mount/unmount operations on a topic in the Redpanda cluster from glossterm:tiered-storage[].
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
+List mount/unmount operations on a topic in the Redpanda cluster from glossterm:Tiered Storage[].
 
 You can also filter the list by state using the `--filter` flag. The possible states are:
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-list-mountable.adoc

@@ -1,6 +1,11 @@
 = rpk cluster storage list-mountable
 // tag::single-source[]
 
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
 List topics that are available to mount from object storage.
 
 This command displays topics that exist in object storage and can be mounted to your Redpanda cluster. Each topic includes its location in object storage and namespace information if applicable.

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-mount.adoc

@@ -1,7 +1,12 @@
 = rpk cluster storage mount
 // tag::single-source[]
 
-Mount a topic to the Redpanda cluster from glossterm:tiered-storage[].
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
+Mount a topic to the Redpanda cluster from glossterm:Tiered Storage[].
 
 This command mounts a topic in the Redpanda cluster using log segments stored in Tiered Storage. 
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-status-mount.adoc

@@ -1,7 +1,12 @@
 = rpk cluster storage status mount
 // tag::single-source[]
 
-Status of mount/unmount operation on topic in a Redpanda cluster from glossterm:tiered-storage[].
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
+Status of mount/unmount operation on topic in a Redpanda cluster from glossterm:Tiered Storage[].
 
 == Usage
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-storage-unmount.adoc

@@ -1,7 +1,12 @@
 = rpk cluster storage unmount
 // tag::single-source[]
 
-Unmount a topic from the Redpanda cluster and secure it in glossterm:tiered-storage[].
+ifdef::env-cloud[]
+NOTE: This command is only supported in BYOC and Dedicated clusters.
+
+endif::[]
+
+Unmount a topic from the Redpanda cluster and secure it in glossterm:Tiered Storage[].
 
 This command performs an operation that: