docs: properties v25.1 (#1244)

Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com>

Author: paulohtb6

modules/manage/pages/cluster-maintenance/cluster-balancing.adoc

@@ -46,11 +46,6 @@ Every Redpanda topic partition forms a Raft group with a single elected leader.
 
 By default, Redpanda enables topic-aware leadership balancing with the xref:reference:cluster-properties.adoc#enable_leader_balancer[`enable_leader_balancer`] property. Automatic partition leadership balancing improves cluster performance by transferring partition leadership from one broker to other replicas. This transfer changes where data is written to first, but leadership transfer does not involve any data transfer.
 
-The xref:reference:cluster-properties.adoc#leader_balancer_mode[`leader_balancer_mode`] property ensures that each shard in a cluster has an equal number of partitions. It determines the movement of leadership for the replica set of a partition. It supports two modes:
-
-* `random_hill_climbing`: This mode randomly searches for potential leadership movements. If it identifies a movement that improves the balance of leaders per shard and the leaders of a given topic per broker, then the leadership change is applied to the cluster. This is the default.
-* `greedy_balanced_shards`: This mode uses a heuristic approach to find leadership movements that better balance leaders per shard. It applies any beneficial movements it finds.
-
 NOTE: In addition to the periodic heartbeat, leadership balancing can also occur when a xref:upgrade:rolling-upgrade.adoc#impact-of-broker-restarts[broker restarts] or when the controller leader changes (such as when a controller partition changes leader). The _controller leader_ manages the entire cluster. For example, when decommissioning a broker, the controller leader creates a reallocation plan for all partition replicas allocated to that broker. The _partition leader_ then handles the reconfiguration for its Raft group.
 
 === Manually change leadership

modules/manage/pages/iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc

@@ -77,7 +77,7 @@ rpk cluster config set \
   iceberg_rest_catalog_authentication_mode=oauth2 \
   iceberg_rest_catalog_client_id=<open-catalog-connection-client-id> \
   iceberg_rest_catalog_client_secret=${secrets.<open-catalog-client-secret-name>} \
-  iceberg_rest_catalog_prefix=<open-catalog-name>
+  iceberg_rest_catalog_warehouse=<open-catalog-name>
 
 # Optional properties:
 # iceberg_translation_interval_ms_default=1000
@@ -111,7 +111,7 @@ iceberg_rest_catalog_endpoint: https://<snowflake-orgname>-<open-catalog-account
 iceberg_rest_catalog_authentication_mode: oauth2
 iceberg_rest_catalog_client_id: <open-catalog-connection-client-id>
 iceberg_rest_catalog_client_secret: <open-catalog-connection-client-secret>
-iceberg_rest_catalog_prefix: <open-catalog-name>
+iceberg_rest_catalog_warehouse: <open-catalog-name>
 
 # Optional
 iceberg_translation_interval_ms_default: 1000

modules/manage/partials/tiered-storage.adoc

@@ -1574,7 +1574,6 @@ Cache trimming helps to balance optimal cache use with the need to avoid blockin
 
 - config_ref:cloud_storage_cache_trim_threshold_percent_objects,true,properties/object-storage-properties[]
 - config_ref:cloud_storage_cache_trim_threshold_percent_size,true,properties/object-storage-properties[]
-- config_ref:cloud_storage_cache_trim_carryover_bytes,true,properties/object-storage-properties[]
 - config_ref:cloud_storage_cache_trim_walk_concurrency,true,properties/object-storage-properties[]
 
 *Recommendations*:
@@ -1632,9 +1631,6 @@ If both this property and `cloud_storage_cache_size` are set, Redpanda uses the
 | Maximum size (in bytes) of the disk cache used by Tiered Storage. +
 If both this property and `cloud_storage_cache_size_percent` are set, Redpanda uses the minimum of the two.
 
-| config_ref:cloud_storage_cache_trim_carryover_bytes,true,properties/object-storage-properties[]
-| The cache performs a recursive directory inspection during the cache trim. The information obtained during the inspection can be carried over to the next trim operation. This property sets a limit on the memory occupied by objects that can be carried over from one trim to next, and it allows the cache to quickly unblock readers before starting the directory inspection.
-
 | config_ref:cloud_storage_cache_trim_threshold_percent_objects,true,properties/object-storage-properties[]
 | Trigger cache trimming when the number of objects in the cache reaches this percentage relative to its maximum object count. If unset, the default behavior is to start trimming when the cache is full.