docs(DOC-732): document partition_autobalancing_node_autodecommission_time

docs-data/property-overrides.json

@@ -421,6 +421,9 @@
     "cloud_storage_min_chunks_per_segment_threshold": {
       "description": "The minimum number of chunks per segment for trimming to be enabled. If the number of chunks in a segment is below this threshold, the segment is small enough that all chunks in it can be hydrated at any given time."
     },
+    "cloud_storage_prefetch_segments_max": {
+      "version": "dev"
+    },
     "cloud_storage_readreplica_manifest_sync_timeout_ms": {
       "description": "Timeout to check if new data is available for partitions in object storage for read replicas."
     },
@@ -488,6 +491,24 @@
       "description": "Configure the addressing style that controls how Redpanda formats bucket URLs for S3-compatible object storage.\n\nLeave this property unset (`null`) to use automatic configuration:\n\n* For AWS S3: Redpanda attempts `virtual_host` addressing first, then falls back to `path` style if needed\n* For MinIO: Redpanda automatically uses `path` style regardless of `MINIO_DOMAIN` configuration\n\nSet this property explicitly to override automatic configuration, ensure consistent behavior across deployments, or when using S3-compatible storage that requires a specific URL format.\n\nCAUTION: 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.\n\nNOTE: 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.",
       "config_scope": "cluster"
     },
+    "cloud_topics_allow_materialization_failure": {
+      "version": "dev"
+    },
+    "cloud_topics_compaction_interval_ms": {
+      "version": "dev"
+    },
+    "cloud_topics_compaction_key_map_memory": {
+      "version": "dev"
+    },
+    "cloud_topics_compaction_max_object_size": {
+      "version": "dev"
+    },
+    "cloud_topics_disable_level_zero_gc_for_tests": {
+      "version": "dev"
+    },
+    "cloud_topics_disable_metastore_flush_loop_for_tests": {
+      "version": "dev"
+    },
     "cloud_topics_disable_reconciliation_loop": {
       "exclude_from_docs": true,
       "config_scope": "cluster"
@@ -504,10 +525,31 @@
       "description": "The duration, in milliseconds, for which a cluster-wide epoch is cached locally on each broker.\n\nCaching the epoch locally reduces the need for frequent coordination with the controller. This property controls how long each broker can use a cached epoch value before fetching the latest value.\n\nIncrease this value to reduce coordination overhead in clusters with stable workloads. Decrease it if you need brokers to react more quickly to epoch changes in Tiered Storage.",
       "version": "v25.3.3"
     },
+    "cloud_topics_fetch_debounce_enabled": {
+      "version": "dev"
+    },
+    "cloud_topics_gc_health_check_interval": {
+      "version": "dev"
+    },
+    "cloud_topics_l1_indexing_interval": {
+      "version": "dev"
+    },
+    "cloud_topics_long_term_file_deletion_delay": {
+      "version": "dev"
+    },
+    "cloud_topics_long_term_flush_interval": {
+      "version": "dev"
+    },
     "cloud_topics_long_term_garbage_collection_interval": {
       "exclude_from_docs": true,
       "config_scope": "cluster"
     },
+    "cloud_topics_parallel_fetch_enabled": {
+      "version": "dev"
+    },
+    "cloud_topics_preregistered_object_ttl": {
+      "version": "dev"
+    },
     "cloud_topics_produce_batching_size_threshold": {
       "exclude_from_docs": true,
       "config_scope": "cluster"
@@ -524,6 +566,27 @@
       "exclude_from_docs": true,
       "config_scope": "cluster"
     },
+    "cloud_topics_reconciliation_max_interval": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_max_object_size": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_min_interval": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_parallelism": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_slowdown_blend": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_speedup_blend": {
+      "version": "dev"
+    },
+    "cloud_topics_reconciliation_target_fill_ratio": {
+      "version": "dev"
+    },
     "cloud_topics_short_term_gc_backoff_interval": {
       "description": "The interval, in milliseconds, between invocations of the L0 garbage collection work loop when no progress is being made or errors are occurring.\n\nL0 (level-zero) objects are short-term data objects in Tiered Storage that are periodically garbage collected. When GC encounters errors or cannot make progress (for example, if there are no objects eligible for deletion), this backoff interval prevents excessive retries.\n\nIncrease this value to reduce system load when GC cannot make progress. Decrease it if you need faster retry attempts after transient errors.",
       "version": "v25.3.3"
@@ -536,6 +599,9 @@
       "description": "The minimum age, in milliseconds, of an L0 (level-zero) object before it becomes eligible for garbage collection.\n\nThis grace period delays deletion of L0 objects even after they become eligible based on epoch. The delay provides a safety buffer that can support recovery in cases involving accidental deletion or other operational issues.\n\nIncrease this value to extend the retention window for L0 objects, providing more time for recovery from operational errors. Decrease it to free up object storage space more quickly, but with less protection against accidental deletion.",
       "version": "v25.3.3"
     },
+    "cloud_topics_upload_part_size": {
+      "version": "dev"
+    },
     "cluster_id": {
       "description": "Cluster identifier.",
       "config_scope": "cluster"
@@ -709,6 +775,9 @@
       ],
       "config_scope": "cluster"
     },
+    "default_redpanda_storage_mode": {
+      "version": "dev"
+    },
     "delete.retention.ms": {
       "description": "The retention time for tombstone records in a compacted topic. Redpanda removes tombstone records after the retention limit is exceeded.\n\nIf you have enabled Tiered Storage and set <<redpandaremoteread,`redpanda.remote.read`>> or <<redpandaremotewrite,`redpanda.remote.write`>> for the topic, you cannot enable tombstone removal.\n\nIf both `delete.retention.ms` and the cluster property config_ref:tombstone_retention_ms,true,properties/cluster-properties[] are set, `delete.retention.ms` overrides the cluster level tombstone retention for an individual topic.\n\nThis property supports three states:\n\n* Positive value: Sets the milliseconds to retain tombstone records before removal.\n* 0: Tombstone records are immediately eligible for removal.\n* Negative value: Disables tombstone removal entirely for this topic.",
       "related_topics": [
@@ -717,6 +786,9 @@
       ],
       "config_scope": "topic"
     },
+    "delete_topic_enable": {
+      "version": "dev"
+    },
     "developer_mode": {
       "description": "CAUTION: Enabling `developer_mode` isn't recommended for production use.\n\nEnable developer mode, which skips most of the checks performed at startup.",
       "config_scope": "broker",
@@ -1028,6 +1100,9 @@
       ],
       "config_scope": "cluster"
     },
+    "internal_rpc_request_timeout_ms": {
+      "version": "dev"
+    },
     "internal_topic_replication_factor": {
       "description": "Target replication factor for internal topics.\n\n*Unit*: number of replicas per topic.",
       "config_scope": "cluster"
@@ -1403,6 +1478,9 @@
       "config_scope": "broker",
       "category": "schema-registry"
     },
+    "nested_group_behavior": {
+      "version": "dev"
+    },
     "node_id": {
       "config_scope": "broker",
       "category": "redpanda",
@@ -1447,6 +1525,9 @@
       "description": "The URL pointing to the well-known discovery endpoint for the OIDC provider.",
       "config_scope": "cluster"
     },
+    "oidc_group_claim_path": {
+      "version": "dev"
+    },
     "oidc_principal_mapping": {
       "description": "Rule for mapping JWT payload claim to a Redpanda user principal.",
       "related_topics": [
@@ -1519,6 +1600,9 @@
       "description": "Controls when and how Redpanda automatically rebalances partition replicas across brokers. For more information, see xref:manage:cluster-maintenance/cluster-balancing.adoc[partition balancing].\n\nValues:\n\n* `continuous`: Partition balancing happens automatically to maintain optimal performance and availability, based on continuous monitoring for node changes (same as `node_add`) and also high disk usage. This option requires an enterprise license, and it is customized by xref:reference:properties/cluster-properties.adoc#partition_autobalancing_node_availability_timeout_sec[`partition_autobalancing_node_availability_timeout_sec`] and xref:reference:properties/cluster-properties.adoc#partition_autobalancing_max_disk_usage_percent[`partition_autobalancing_max_disk_usage_percent`] properties.\n* `node_add`: Partition balancing happens when a node is added.\n* `off`: Partition balancing is disabled. This option is not recommended for production clusters.",
       "config_scope": "cluster"
     },
+    "partition_autobalancing_node_autodecommission_timeout_sec": {
+      "version": "dev"
+    },
     "partition_autobalancing_node_availability_timeout_sec": {
       "related_topics": [
         "xref:manage:cluster-maintenance/continuous-data-balancing.adoc[Configure Continuous Data Balancing]"
@@ -1701,6 +1785,9 @@
       ],
       "config_scope": "topic"
     },
+    "redpanda.storage.mode": {
+      "version": "dev"
+    },
     "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": [
@@ -1897,6 +1984,9 @@
       "related_topics": [],
       "config_scope": "cluster"
     },
+    "schema_registry_enable_qualified_subjects": {
+      "version": "dev"
+    },
     "schema_registry_replication_factor": {
       "description": "Replication factor for internal `_schemas` topic. If unset, defaults to the xref:../cluster-properties.adoc#default_topic_replication[`default_topic_replication`] cluster property.",
       "related_topics": [