auto-docs: Update property docs for tag v26.1.2

antora.yml

@@ -17,8 +17,8 @@ asciidoc:
     # Fallback versions
     # We try to fetch the latest versions from GitHub at build time
     # --
-    full-version: 26.1.1
-    latest-redpanda-tag: 'v26.1.1'
+    full-version: 26.1.2
+    latest-redpanda-tag: 'v26.1.2'
     latest-console-tag: 'v3.3.1'
     latest-release-commit: '35a825c9c1880ebeedf4c18bb8c6cceaa63566c1'
     latest-operator-version: 'v2.3.8-24.3.6'

docs-data/property-overrides.json

@@ -775,7 +775,7 @@
       "config_scope": "cluster"
     },
     "default_redpanda_storage_mode": {
-      "description": "Set the default storage mode for new topics. This value applies to any topic created without an explicit <<redpandastoragemode,`redpanda.storage.mode`>> setting (that is, when the topic's `redpanda.storage.mode` is `unset`).\n\nAccepted values:\n\n* `unset`: Defer to the legacy <<cloud_storage_enable_remote_read,`redpanda.remote.read`>> and <<cloud_storage_enable_remote_write,`redpanda.remote.write`>> topic properties for Tiered Storage configuration.\n* `local`: Store data only on local disks, with no object storage involvement.\n* `tiered`: Store data on local disks and replicate it to object storage using Tiered Storage. Equivalent to setting `redpanda.remote.read` and `redpanda.remote.write` to `true`.\n* `cloud`: Store data primarily in object storage using Cloud Topics.",
+      "description": "Set the default storage mode for new topics. This value applies to any topic created without an explicit <<redpandastoragemode,`redpanda.storage.mode`>> setting (that is, when the topic's `redpanda.storage.mode` is `unset`).\n\nAccepted values:\n\n* `unset`: Defer to the legacy <<cloud_storage_enable_remote_read,`redpanda.remote.read`>> and <<cloud_storage_enable_remote_write,`redpanda.remote.write`>> topic properties for Tiered Storage configuration.\n* `local`: Store data only on local disks, with no object storage involvement.\nifndef::env-cloud[]\n* `tiered`: Store data on local disks and replicate it to object storage using xref:manage:tiered-storage.adoc[Tiered Storage]. Equivalent to setting `redpanda.remote.read` and `redpanda.remote.write` to `true`.\n* `cloud`: Store data primarily in object storage using xref:develop:manage-topics/cloud-topics.adoc[Cloud Topics].\nendif::[]\nifdef::env-cloud[]\n* `tiered`: Store data on local disks and replicate it to object storage using Tiered Storage. Equivalent to setting `redpanda.remote.read` and `redpanda.remote.write` to `true`.\n* `cloud`: Store data primarily in object storage using Cloud Topics.\nendif::[]",
       "related_topics": [
         "self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]",
         "self-managed-only: xref:develop:manage-topics/cloud-topics.adoc[Manage Cloud Topics]"
@@ -1092,14 +1092,14 @@
       "config_scope": "topic"
     },
     "initial_retention_local_target_bytes_default": {
-      "description": "Initial local retention size target for partitions of topics with Tiered Storage enabled. If no initial local target retention is configured, then  all locally-retained data will be delivered to learner when joining the partition replica set.",
+      "description": "ifndef::env-cloud[]\nInitial local retention size target for partitions of topics with xref:manage:tiered-storage.adoc[Tiered Storage] enabled. If no initial local target retention is configured, then all locally-retained data will be delivered to the learner when joining the partition replica set.\nendif::[]\nifdef::env-cloud[]\nInitial local retention size target for partitions of topics with Tiered Storage enabled. If no initial local target retention is configured, then all locally-retained data will be delivered to the learner when joining the partition replica set.\nendif::[]",
       "related_topics": [
         "self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]"
       ],
       "config_scope": "cluster"
     },
     "initial_retention_local_target_ms_default": {
-      "description": "Initial local retention time target for partitions of topics with Tiered Storage enabled. If no initial local target retention is configured, then all locally-retained data will be delivered to the learner when joining the partition replica set.",
+      "description": "ifndef::env-cloud[]\nInitial local retention time target for partitions of topics with xref:manage:tiered-storage.adoc[Tiered Storage] enabled. If no initial local target retention is configured, then all locally-retained data will be delivered to the learner when joining the partition replica set.\nendif::[]\nifdef::env-cloud[]\nInitial local retention time target for partitions of topics with Tiered Storage enabled. If no initial local target retention is configured, then all locally-retained data will be delivered to the learner when joining the partition replica set.\nendif::[]",
       "related_topics": [
         "self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]"
       ],
@@ -1296,6 +1296,12 @@
       "description": "Leadership rebalancing idle timeout.\n\n*Unit*: milliseconds",
       "config_scope": "cluster"
     },
+    "leader_balancer_mode": {
+      "_comment": "greedy mode excluded from docs - internal use only (added in v26.1.2)",
+      "description": "Mode of the leader balancer optimization strategy.\n\nAccepted values:\n\n* `calibrated` (default): An adaptive strategy that samples potential moves and prioritizes high-impact transfers. Minimizes unnecessary leader movement while achieving balance over time. Best for most production workloads.\n* `random`: Accepts the first random move that improves balance. Less efficient than `calibrated` because it doesn't prioritize high-impact moves. Available as a fallback if `calibrated` causes unexpected behavior.\n\nLegacy values `greedy_balanced_shards` and `random_hill_climbing` are treated as `calibrated`.",
+      "accepted_values": ["calibrated", "random"],
+      "config_scope": "cluster"
+    },
     "leader_balancer_mute_timeout": {
       "description": "The length of time that a glossterm:Raft[] group is muted after a leadership rebalance operation. Any group that has been moved, regardless of whether the move succeeded or failed, undergoes a cooling-off period. This prevents Raft groups from repeatedly experiencing leadership rebalance operations in a short time frame, which can lead to instability in the cluster.\n\nThe leader balancer maintains a list of muted groups and reevaluates muted status at the start of each balancing iteration. Muted groups still contribute to overall cluster balance calculations although they can't themselves be moved until the mute period is over.",
       "config_scope": "cluster"
@@ -1795,7 +1801,7 @@
       "config_scope": "topic"
     },
     "redpanda.storage.mode": {
-      "description": "The storage mode for a topic. Determines how topic data is stored and whether it is eligible for upload to object storage.\n\nAccepted values:\n\n* `local`: Topic data is stored only on the broker's local disk. Object storage upload is disabled for the topic, regardless of cluster-level Tiered Storage settings.\n* `tiered`: Topic data is stored on local disk and also uploaded to object storage. Enables Tiered Storage for the topic.\n* `cloud`: Topic data is stored in object storage using the Cloud Topics architecture. Local storage is used only as a write buffer.\n* `unset`: Specifies that the topic's storage mode is unset, regardless of the cluster default. The topic may still have Tiered Storage enabled through the legacy properties `redpanda.remote.read` and `redpanda.remote.write`.\n\nThis property overrides the cluster-wide config_ref:default_redpanda_storage_mode,true,properties/cluster-properties[] setting for individual topics.",
+      "description": "The storage mode for a topic. Determines how topic data is stored and whether it is eligible for upload to object storage.\n\nAccepted values:\n\n* `local`: Topic data is stored only on the broker's local disk. Object storage upload is disabled for the topic, regardless of cluster-level Tiered Storage settings.\nifndef::env-cloud[]\n* `tiered`: Topic data is stored on local disk and also uploaded to object storage. Enables xref:manage:tiered-storage.adoc[Tiered Storage] for the topic.\n* `cloud`: Topic data is stored in object storage using the xref:develop:manage-topics/cloud-topics.adoc[Cloud Topics] architecture. Local storage is used only as a write buffer.\nendif::[]\nifdef::env-cloud[]\n* `tiered`: Topic data is stored on local disk and also uploaded to object storage. Enables Tiered Storage for the topic.\n* `cloud`: Topic data is stored in object storage using the Cloud Topics architecture. Local storage is used only as a write buffer.\nendif::[]\n* `unset`: Specifies that the topic's storage mode is unset, regardless of the cluster default. The topic may still have Tiered Storage enabled through the legacy properties `redpanda.remote.read` and `redpanda.remote.write`.\n\nThis property overrides the cluster-wide config_ref:default_redpanda_storage_mode,true,properties/cluster-properties[] setting for individual topics.",
       "related_topics": [
         "self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]",
         "self-managed-only: xref:develop:manage-topics/cloud-topics.adoc[Manage Cloud Topics]"
@@ -2261,4 +2267,4 @@
       "description": "The default write caching mode to apply to user topics. Write caching acknowledges a message as soon as it is received and acknowledged on a majority of brokers, without waiting for it to be written to disk. With `acks=all`, this provides lower latency while still ensuring that a majority of brokers acknowledge the write. \n\nFsyncs follow <<raft_replica_max_pending_flush_bytes,`raft_replica_max_pending_flush_bytes`>> and <<raft_replica_max_flush_delay_ms,`raft_replica_max_flush_delay_ms`>>, whichever is reached first.\n\nThe `write_caching_default` cluster property can be overridden with the xref:reference:properties/topic-properties.adoc#writecaching[`write.caching`] topic property."
     }
   }
-}
+}

docs-data/redpanda-property-changes-v26.1.1-to-v26.1.1-rc5.json → docs-data/redpanda-property-changes-v26.1.1-to-v26.1.2.json

@@ -1,15 +1,16 @@
 {
   "comparison": {
     "oldVersion": "v26.1.1",
-    "newVersion": "v26.1.1-rc5",
-    "timestamp": "2026-03-31T14:37:03.774Z"
+    "newVersion": "v26.1.2",
+    "timestamp": "2026-04-03T17:46:32.769Z"
   },
   "summary": {
     "newProperties": 0,
     "changedDefaults": 0,
     "changedDescriptions": 0,
     "changedTypes": 0,
     "deprecatedProperties": 0,
+    "removedDeprecatedProperties": 0,
     "removedProperties": 0,
     "emptyDescriptions": 2
   },
@@ -19,6 +20,7 @@
     "changedDescriptions": [],
     "changedTypes": [],
     "deprecatedProperties": [],
+    "removedDeprecatedProperties": [],
     "removedProperties": [],
     "emptyDescriptions": [
       {