Merge branch 'rpk-v25.1.9' into rpk-v25.2

Author: paulohtb6

.github/workflows/get-cloud-api-spec.yml

@@ -36,20 +36,23 @@ jobs:
 
       - name: Get commit SHA and build URL
         id: commit-info
+        working-directory: redpanda-docs
         run: |
           COMMIT_SHA="${{ github.event.client_payload.commit_sha }}"
           COMMIT_URL="https://github.com/redpanda-data/cloudv2/commit/${COMMIT_SHA}"
           echo "COMMIT_SHA=${COMMIT_SHA}" >> $GITHUB_ENV
           echo "COMMIT_URL=${COMMIT_URL}" >> $GITHUB_ENV
 
       - name: Install dependencies
+        working-directory: redpanda-docs
         run: |
           npm install
 
       - name: Run the script and save the output
+        working-directory: redpanda-docs
         run: |
-          npx doc-tools fetch -o redpanda-data -r cloudv2 -p proto/gen/openapi/openapi.controlplane.prod.yaml -d ../../modules/ROOT/attachments cloud-controlplane-api.yaml
-          npx doc-tools fetch -o redpanda-data -r cloudv2 -p proto/gen/openapi/openapi.dataplane.prod.yaml -d ../../modules/ROOT/attachments cloud-dataplane-api.yaml
+          npx doc-tools fetch -o redpanda-data -r cloudv2 -p proto/gen/openapi/openapi.controlplane.prod.yaml -d modules/ROOT/attachments -f cloud-controlplane-api.yaml
+          npx doc-tools fetch -o redpanda-data -r cloudv2 -p proto/gen/openapi/openapi.dataplane.prod.yaml -d  modules/ROOT/attachments -f cloud-dataplane-api.yaml
         env:
           VBOT_GITHUB_API_TOKEN: ${{ env.ACTIONS_BOT_TOKEN }}
       - name: Create pull request

modules/console/pages/index.adoc

@@ -34,7 +34,8 @@ image::topic.png[]
 Manage Redpanda users and control who has access to Redpanda Console:
 
 * *Visual ACL management*: Create, view, and manage ACLs, ensuring that your data is secure and access is properly controlled.
-* *Identity provider integration*: For enterprise users, Redpanda Console integrates with identity providers (IDP) for single sign-on (SSO), making user management straightforward and secure.
+* *Rotate credentials*: Update user and service account passwords to maintain security without downtime.
+* *Identity provider integration*: For enterprise users, Redpanda Console integrates with identity providers (IdPs) for single sign-on (SSO), making user management straightforward and secure.
 
 image::user.png[]
 

modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc

@@ -14,12 +14,24 @@ Throughput and retention requirements can cause bottlenecks in the system. On an
 
 In general, choose the number of nodes based on the following criteria, and add nodes for fault tolerance. This ensures that the system can operate with full throughput in a degraded state.
 
-* Total network bandwidth must account for maximum simultaneous writes and reads, multiplied by the replication factor.
-* Have a minimum of 2 GB memory for each core, but more memory is better.
-* Have a minimum of 4 MB of memory for each topic partition replica. You can enforce this requirement in the tunable xref:reference:tunable-properties.adoc#topic_memory_per_partition[`topic_memory_per_partition` property].
-* Use Tiered Storage to unify historical and real-time data.
-* For AWS, test with either i3en, i4i, or is4gen; for GCP, test with n2-standard (GCP); and for Azure, test with lsv2. In general, choose instance types that prioritize storage and network performance.
-* Run hardware and Redpanda benchmark tests for a performance baseline.
+* **Network bandwidth**: Total bandwidth must account for maximum simultaneous writes and reads, multiplied by the replication factor.
+* **Memory per core**: Allocate a minimum of 2 GB memory for each CPU core. Additional memory could improve performance.
+* **Memory per partition**: Allocate a minimum of 2 MB of memory for each topic partition replica. 
++
+For example: If you have 10,000 total partitions with a replication factor of 3, you need at least 60 GB of memory across all brokers:
++
+10,000 partitions × 3 replicas × 2 MB = 60,000 MB (60 GB) 
++
+If these partitions are evenly distributed across three brokers, each broker needs at least 20 GB of memory.
+* **Storage strategy**: Use Tiered Storage to unify historical and real-time data cost-effectively.
+* **Performance testing**: Run hardware and Redpanda benchmark tests to establish a performance baseline. Choose instance types that prioritize storage and network performance:
++
+--
+* **AWS**: Test with i3en (NVMe SSD), i4i (NVMe), or is4gen (Intel-based NVMe) instances, or other NVMe-backed types
+* **Azure**: Test with Lsv2-series instances (high I/O performance) or other high-performance storage types
+* **GCP**: Test with n2-standard instances with local SSD or other high-performance local storage types
+--
+
 
 == Sizing considerations
 

modules/reference/pages/internal-metrics-reference.adoc

@@ -18,6 +18,10 @@ curl http://<node-addr>:9644/metrics | grep "[HELP|TYPE]"
 ----
 ====
 
+Internal metrics (`/metrics`) can generate thousands of metric series in production environments, so use them judiciously in monitoring systems to avoid performance issues. For alerting and dashboards, public metrics are preferable (`/public_metrics`) because they are optimized for lower cardinality.
+
+The xref:reference:properties/cluster-properties.adoc#aggregate_metrics[aggregate_metrics] cluster property controls internal metrics cardinality. When you enable this property, internal metrics combine labels (like shard) to reduce the number of series. Public metrics always combine labels, regardless of this setting.
+
 == vectorized_alien_receive_batch_queue_length
 
 Indicates the current length of the alien receive batch queue.

modules/reference/pages/properties/object-storage-properties.adoc

@@ -1712,23 +1712,32 @@ Maximum backoff interval when there is nothing to upload for a partition, in mil
 
 === cloud_storage_url_style
 
-Specifies the addressing style to use for Amazon S3 requests. This configuration determines how S3 bucket URLs are formatted. Path style is supported for backward compatibility with legacy systems. 
+Configure the addressing style that controls how Redpanda formats bucket URLs for S3-compatible object storage.
 
-When this property is not set (`null`), the client tries to use `virtual_host` addressing. 
+Leave this property unset (`null`) to use automatic configuration:
 
-If the initial request fails, the client automatically tries the `path` style. 
+* For AWS S3: Redpanda attempts `virtual_host` addressing first, then falls back to `path` style if needed
+* For MinIO: Redpanda automatically uses `path` style regardless of `MINIO_DOMAIN` configuration
 
-If neither addressing style works, Redpanda terminates the startup, requiring manual configuration to proceed.
+Set this property explicitly to override automatic configuration, ensure consistent behavior across deployments, or when using S3-compatible storage that requires a specific URL format.
+
+CAUTION: AWS requires virtual-hosted addressing for buckets created after September 30, 2020. If you use AWS S3 with buckets created after this date, use `virtual_host` addressing.
+
+NOTE: For MinIO deployments, Redpanda defaults to `path` style when this property is unset. To use `virtual_host` addressing with a configured `MINIO_DOMAIN`, set this property explicitly to `virtual_host`. For other S3-compatible storage backends, consult your provider's documentation to determine the required URL style.
 
 *Requires restart:* Yes
 
 *Visibility:* `user`
 
-*Accepted values:* 
+*Type:* string
+
+*Accepted values:* [`virtual_host`, `path`, `null`]
+
+*Example formats:*
 
 * `virtual_host` - Example: `<bucket-name>.s3.amazonaws.com` 
 * `path` - Example: `s3.amazonaws.com/<bucket-name>`
-* `null`
+* `null` - Enable automatic configuration
 
 *Default:* `null`
 

modules/reference/pages/public-metrics-reference.adoc

@@ -4,13 +4,24 @@
 
 This section provides reference descriptions for the public metrics exported from Redpanda's `/public_metrics` endpoint.
 
-include::reference:partial$public_metrics_tip.adoc[]
-
 // Cloud does not expose the internal metrics.
 ifndef::env-cloud[]
 include::shared:partial$metrics-usage-tip.adoc[]
 endif::[]
 
+[IMPORTANT]
+====
+In a live system, Redpanda metrics are exported only for features that are in use. For example, Redpanda does not export metrics for consumer groups if no groups are registered.
+
+To see the available public metrics in your system, query the `/public_metrics` endpoint:
+
+[,bash]
+----
+curl http://<node-addr>:9644/public_metrics | grep "[HELP|TYPE]"
+----
+
+====
+
 == Cluster metrics
 
 === redpanda_cluster_brokers
@@ -634,6 +645,10 @@ Total time (in seconds) the CPU has been actively processing tasks.
 
 *Usage*: Useful for tracking overall CPU utilization.
 
+*Labels*:
+
+* `shard`
+
 ---
 
 === redpanda_io_queue_total_read_ops
@@ -646,7 +661,7 @@ Cumulative count of read operations processed by the I/O queue.
 
 * `class=("default" | "compaction" | "raft")`
 
-* `ioshard`
+* `iogroup`
 
 * `mountpoint`
 
@@ -664,7 +679,7 @@ Cumulative count of write operations processed by the I/O queue.
 
 * `class=("default" | "compaction" | "raft")`
 
-* `ioshard`
+* `iogroup`
 
 * `mountpoint`
 
@@ -834,6 +849,14 @@ Alert indicator for cache storage free space, where:
 
 ---
 
+=== redpanda_storage_cache_disk_total_bytes
+
+Total size of attached storage, in bytes.
+
+*Type*: gauge
+
+---
+
 === redpanda_storage_disk_free_bytes
 
 Amount of free disk space (in bytes) available on attached storage.
@@ -1191,6 +1214,11 @@ Total number of records fetched from a topic.
 
 *Type*: counter
 
+*Labels*:
+
+* `redpanda_namespace`
+* `redpanda_topic`
+
 ---
 
 === redpanda_kafka_records_produced_total
@@ -1199,6 +1227,11 @@ Total number of records produced to a topic.
 
 *Type*: counter
 
+*Labels*:
+
+* `redpanda_namespace`
+* `redpanda_topic`
+
 ---
 
 === redpanda_kafka_replicas
@@ -1826,6 +1859,34 @@ Indicator of whether a resource has at least one valid TLS certificate installed
 
 ---
 
+=== redpanda_trust_file_crc32c
+
+CRC32C checksum calculated from the contents of the trust file. This value is calculated when a valid certificate is loaded and a trust store is present. Otherwise, the value is zero.
+
+*Type*: gauge
+
+*Labels*:
+
+- `area`
+- `detail`
+- `shard`
+
+---
+
+=== redpanda_truststore_expires_at_timestamp_seconds
+
+Expiry time of the shortest-lived CA in the truststore, measured in seconds since epoch.
+
+*Type*: gauge
+
+*Labels*:
+
+- `area`
+- `detail`
+- `shard`
+
+---
+
 [[data_transform_metrics]]
 == Data transforms metrics
 

modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc

@@ -43,7 +43,7 @@ rpk cluster self-test start [flags]
 
 |--cloud-backoff-ms |uint | The backoff in milliseconds for a cloud storage request (default `100`).
 
-|--cloud-timeout-ms |uint | The timeout in milliseconds for a cloud storage request (default `5000`).
+|--cloud-timeout-ms |uint | The timeout in milliseconds for a cloud storage request (default `10000`).
 
 |--disk-duration-ms |uint | The duration in milliseconds of individual
 disk test runs (default `30000`).

modules/reference/pages/rpk/rpk-debug/rpk-debug-bundle.adoc

@@ -119,7 +119,7 @@ time. Default: `12s`.
 |--metrics-samples |int |Number of metrics samples to take (at the interval of `--metrics-interval`). Must be higher or equals 2 (default 2).
 
 |-n, --namespace |string |The Kubernetes namespace in which the Redpanda
-cluster is running. Default: `redpanda` +
+cluster is running. +
 *Kubernetes only*.
 
 |-o, --output |string |The file path where the debug file will be

modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-download.adoc

@@ -29,6 +29,8 @@ rpk debug remote-bundle download [flags]
 
 |-o, --output |string |The file path where the debug file will be written (default `./<timestamp>-remote-bundle.zip`).
 
+|--upload-url |string |If provided, where to upload the bundle in addition to creating a copy on disk.
+
 |--config |string |Redpanda or `rpk` config file; default search paths are `/var/lib/redpanda/.config/rpk/rpk.yaml`, `$PWD/redpanda.yaml`, and `/etc/redpanda/redpanda.yaml`.
 
 |-X, --config-opt |stringArray |Override `rpk` configuration settings. See xref:reference:rpk/rpk-x-options.adoc[`rpk -X`] or execute `rpk -X help` for inline detail or `rpk -X list` for terser detail.

modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-start.adoc

@@ -41,7 +41,7 @@ rpk debug remote-bundle start [flags]
 
 |--metrics-samples |int |Number of metrics samples to take (at the interval of `--metrics-interval` flag). Must be >= `2` (default `2`).
 
-|-n, --namespace |string |(K8s only) The namespace to use to collect the resources from (default `redpanda`).
+|-n, --namespace |string |(K8s only) The namespace to use to collect the resources from.
 
 |--no-confirm |- |Disable confirmation prompt.