Merge main into v-WIP/26.1 and prepare for 26.1 GA release

- Merge all commits from main (20 commits)
- Resolve conflicts: keep v-WIP/26.1 version and release notes
- Update antora.yml with v26.1.1 release information:
  - latest-redpanda-tag: v26.1.1
  - latest-release-commit: 35a825c9c1880ebeedf4c18bb8c6cceaa63566c1
  - full-version: 26.1.1
  - page-release-date: 2026-03-31

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: JakeSCahill

.github/ai-opt-out

@@ -0,0 +1 @@
+opt-out: true

antora.yml

@@ -18,9 +18,9 @@ asciidoc:
     # We try to fetch the latest versions from GitHub at build time
     # --
     full-version: 26.1.1
-    latest-redpanda-tag: 'v25.3.7'
+    latest-redpanda-tag: 'v26.1.1'
     latest-console-tag: 'v3.3.1'
-    latest-release-commit: '6aa5af28b020b66e5caa966094882b7260497a53'
+    latest-release-commit: '35a825c9c1880ebeedf4c18bb8c6cceaa63566c1'
     latest-operator-version: 'v2.3.8-24.3.6'
     operator-beta-tag: ''
     helm-beta-tag: ''

docs-data/property-overrides.json

@@ -318,6 +318,10 @@
     "cloud_storage_garbage_collect_timeout_ms": {
       "description": "Timeout for running the cloud storage garbage collection, in milliseconds."
     },
+    "cloud_storage_gc_max_segments_per_run": {
+      "version": "v25.3.11",
+      "description": "Maximum number of log segments to delete from object storage during each housekeeping run. This limits the rate of object deletions to prevent overwhelming the object storage API. Each segment requires 2-3 object storage delete operations (for the data file, index file, and optionally a transaction manifest), so this value directly controls API request rate. See xref:manage:tiered-storage.adoc#object-storage-housekeeping[Object storage housekeeping]."
+    },
     "cloud_storage_graceful_transfer_timeout_ms": {
       "description": "Time limit on waiting for uploads to complete before a leadership transfer.  If this is `null`, leadership transfers proceed without waiting."
     },
@@ -774,7 +778,7 @@
       "related_topics": [
         "xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]"
       ],
-      "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.",
+      "description": "Controls whether Redpanda validates schema IDs in records and which topic properties are enforced.\n\nValues:\n\n* `none`: Schema validation is disabled (no schema ID checks are done). Associated topic properties cannot be modified.\n* `redpanda`: Schema validation is enabled. Only Redpanda topic properties are accepted.\n* `compat`: Schema validation is enabled. Both Redpanda and compatible topic properties are accepted.\n\nNOTE: Enabling this property will trigger decompression of message batches for topics on which validation is configured, which may lead to a modest increase in CPU load. Redpanda recommends monitoring CPU utilization after topics are configured.",
       "config_scope": "cluster"
     },
     "enable_shadow_linking": {
@@ -829,7 +833,7 @@
       "config_scope": "cluster"
     },
     "iceberg_default_catalog_namespace": {
-      "description": "The default namespace (database name) for Iceberg tables. All tables created by Redpanda will be placed in this namespace within the Iceberg catalog. Supports nested namespaces as an array of strings.\n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
+      "description": "The default Iceberg catalog namespace where Redpanda creates tables. Supports nested namespaces as an array of strings.\n\nIMPORTANT: This value must be configured before enabling Iceberg and must not be changed afterward. Changing it will cause Redpanda to lose track of existing tables.",
       "version": "v25.3.5"
     },
     "iceberg_default_partition_spec": {
@@ -1132,6 +1136,7 @@
       "config_scope": "cluster"
     },
     "kafka_fetch_request_timeout_ms": {
+      "description": "Target duration for a single fetch request. The broker tries to complete each fetch within this duration, even if fewer bytes are available than requested.",
       "version": "v25.3.7"
     },
     "kafka_max_message_size_upper_limit_bytes": {
@@ -1215,6 +1220,10 @@
       "description": "Prevents log compaction from removing transaction metadata. Only set this to `true` if you experience stability issues related to transaction cleanup during compaction.",
       "config_scope": "cluster"
     },
+    "log_compaction_max_priority_wait_ms": {
+      "description": "Maximum time a priority partition (for example, `__consumer_offsets`) can wait for compaction before preempting regular compaction.",
+      "version": "v25.3.8"
+    },
     "log_compaction_merge_max_ranges": {
       "description": "The maximum range of segments that can be processed in a single round of adjacent segment compaction. If `null` (the default value), no maximum is imposed on the number of ranges that can be processed at once. A value below 1 effectively disables adjacent merge compaction.",
       "config_scope": "cluster"
@@ -1824,6 +1833,26 @@
       "description": "Path to RPK binary.",
       "config_scope": "cluster"
     },
+    "rps_limit_acls_and_users_operations": {
+      "description": "Rate limit, in requests per second, for ACL and user operations on the controller. The controller processes cluster management requests (such as creating, deleting, and updating ACLs and users) through the controller log (raft0).",
+      "config_scope": "cluster"
+    },
+    "rps_limit_configuration_operations": {
+      "description": "Rate limit, in requests per second, for configuration operations on the controller. The controller processes cluster management requests (such as cluster configuration updates, feature activations, and data policy changes) through the controller log (raft0).",
+      "config_scope": "cluster"
+    },
+    "rps_limit_move_operations": {
+      "description": "Rate limit, in requests per second, for move operations on the controller. The controller processes cluster management requests (such as moving and canceling partition replica reassignments) through the controller log (raft0).",
+      "config_scope": "cluster"
+    },
+    "rps_limit_node_management_operations": {
+      "description": "Rate limit, in requests per second, for node management operations on the controller. The controller processes cluster management requests (such as decommissioning, recommissioning, and setting brokers to maintenance mode) through the controller log (raft0).",
+      "config_scope": "cluster"
+    },
+    "rps_limit_topic_operations": {
+      "description": "Rate limit, in requests per second, for topic operations on the controller. The controller processes cluster management requests (such as creating, deleting, and updating topics and partition counts) through the controller log (raft0).",
+      "config_scope": "cluster"
+    },
     "sasl_mechanism": {
       "description": "The SASL mechanism to use when the HTTP Proxy client connects to the Kafka API. These credentials are used when the HTTP Proxy API listener has <<http_proxy_auth_method, `authentication_method`>>: `none` but the cluster requires authenticated access to the Kafka API.\n\nThis property specifies which individual SASL mechanism the HTTP Proxy client should use, while the cluster-wide available mechanisms are configured using the xref:reference:properties/cluster-properties.adoc#sasl_mechanisms[`sasl_mechanisms`] cluster property.\n\ninclude::shared:partial$http-proxy-ephemeral-credentials-breaking-change.adoc[]\n\nNOTE: While the cluster-wide xref:reference:properties/cluster-properties.adoc#sasl_mechanisms[`sasl_mechanisms`] property may support additional mechanisms (PLAIN, GSSAPI, OAUTHBEARER), HTTP Proxy client connections only support SCRAM mechanisms.",
       "related_topics": [
@@ -1864,6 +1893,9 @@
       "config_scope": "broker",
       "category": "schema-registry"
     },
+    "schema_registry_avro_use_named_references": {
+      "version": "v25.3.10"
+    },
     "schema_registry_enable_authorization": {
       "description": "Enables ACL-based authorization for Schema Registry requests. When `true`, Schema Registry\nuses ACL-based authorization instead of the default `public/user/superuser` authorization model.",
       "related_topics": [],

…property-changes-v25.3.5-to-v25.3.7.json …operty-changes-v25.3.10-to-v25.3.11.jsondocs-data/redpanda-property-changes-v25.3.5-to-v25.3.7.json renamed to docs-data/redpanda-property-changes-v25.3.10-to-v25.3.11.json docs-data/redpanda-property-changes-v25.3.5-to-v25.3.7.json renamed to docs-data/redpanda-property-changes-v25.3.10-to-v25.3.11.json

@@ -1,31 +1,33 @@
 {
   "comparison": {
-    "oldVersion": "v25.3.5",
-    "newVersion": "v25.3.7",
-    "timestamp": "2026-02-07T17:24:45.753Z"
+    "oldVersion": "v25.3.10",
+    "newVersion": "v25.3.11",
+    "timestamp": "2026-03-26T03:19:25.076Z"
   },
   "summary": {
     "newProperties": 1,
     "changedDefaults": 0,
     "changedDescriptions": 0,
     "changedTypes": 0,
     "deprecatedProperties": 0,
+    "removedDeprecatedProperties": 0,
     "removedProperties": 0,
     "emptyDescriptions": 3
   },
   "details": {
     "newProperties": [
       {
-        "name": "kafka_fetch_request_timeout_ms",
+        "name": "cloud_storage_gc_max_segments_per_run",
         "type": "integer",
-        "default": 5000,
-        "description": "Broker-side target for the duration of a single fetch request. The broker will try to complete fetches within the specified duration, even if it means returning less bytes in the fetch than are available."
+        "default": 300,
+        "description": "Maximum number of segments to delete per housekeeping run. Each segment maps to up to three object keys (data, index, tx manifest), so a value of 300 produces 600 to 900 deletes plus one per spillover manifest."
       }
     ],
     "changedDefaults": [],
     "changedDescriptions": [],
     "changedTypes": [],
     "deprecatedProperties": [],
+    "removedDeprecatedProperties": [],
     "removedProperties": [],
     "emptyDescriptions": [
       {

modules/ROOT/nav.adoc

@@ -193,6 +193,7 @@
 **** xref:manage:iceberg/iceberg-topics-gcp-biglake.adoc[GCP BigLake]
 **** xref:manage:iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc[Snowflake and Open Catalog]
 *** xref:manage:iceberg/query-iceberg-topics.adoc[Query Iceberg Topics]
+*** xref:manage:iceberg/migrate-to-iceberg-topics.adoc[Migrate to Iceberg Topics]
 ** xref:manage:schema-reg/index.adoc[Schema Registry]
 *** xref:manage:schema-reg/schema-reg-overview.adoc[Overview]
 *** xref:manage:schema-reg/manage-schema-reg.adoc[]