Update Properties with the latest in v26.1

docs-data/property-overrides.json

@@ -682,6 +682,13 @@
       "description": "Size of the scratch space datalake soft limit expressed as a percentage of the `datalake_scratch_space_size_bytes` configuration value.",
       "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.\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 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:manage:tiered-storage.adoc#cloud-topics[cloud topics].",
+      "related_topics": [
+        "xref:manage:tiered-storage.adoc[Tiered Storage]"
+      ],
+      "config_scope": "cluster"
+    },
     "default_leaders_preference": {
       "description": "Default settings for preferred location of topic partition leaders. It can be either \"none\" (no preference), or \"racks:<rack1>,<rack2>,...\" (prefer brokers with rack ID from the list).\n\nThe list can contain one or more rack IDs. If you specify multiple IDs, Redpanda tries to distribute the partition leader locations equally across brokers in these racks.\n\nIf config_ref:enable_rack_awareness,true,properties/cluster-properties[] is set to `false`, leader pinning is disabled across the cluster.",
       "related_topics": [
@@ -1676,6 +1683,13 @@
       ],
       "config_scope": "topic"
     },
+    "redpanda.storage.mode": {
+      "description": "Set the storage mode for this topic, controlling where Redpanda stores its data. This property supersedes the legacy <<redpandaremoteread,`redpanda.remote.read`>> and <<redpandaremotewrite,`redpanda.remote.write`>> properties.\n\nYou can set this value at topic creation time or alter it later, although only certain transitions between modes are allowed.\n\nAccepted values:\n\n* `unset`: Defer to the legacy `redpanda.remote.read` and `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 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:manage:tiered-storage.adoc#cloud-topics[cloud topics].\n\nIf not set explicitly, the topic inherits the cluster-level default from config_ref:default_redpanda_storage_mode,true,properties/cluster-properties[].",
+      "related_topics": [
+        "xref:manage:tiered-storage.adoc[Tiered Storage]"
+      ],
+      "config_scope": "topic"
+    },
     "redpanda.value.schema.id.validation": {
       "description": "Enable validation of the schema ID for values on a record. When enabled, Redpanda validates that the schema ID encoded in the record's value is registered in the Schema Registry according to the configured subject name strategy.",
       "related_topics": [