Merge pull request #73814 from kowen-rh/ocpbugs-29848

OCPBUGS#29848: Update etcd hard drive best practices

Author: stevsmit

modules/recommended-etcd-practices.adoc

@@ -20,15 +20,14 @@ To achieve such performance, run etcd on machines that are backed by SSD or NVMe
 The load on etcd arises from static factors, such as the number of nodes and pods, and dynamic factors, including changes in endpoints due to pod autoscaling, pod restarts, job executions, and other workload-related events. To accurately size your etcd setup, you must analyze the specific requirements of your workload. Consider the number of nodes, pods, and other relevant factors that impact the load on etcd.
 ====
 
-The following hard disk features provide optimal etcd performance:
-
-* Low latency to support fast read operation.
-* High-bandwidth writes for faster compactions and defragmentation.
-* High-bandwidth reads for faster recovery from failures.
-* Solid state drives as a minimum selection, however NVMe drives are preferred.
-* Server-grade hardware from various manufacturers for increased reliability.
-* RAID 0 technology for increased performance.
-* Dedicated etcd drives. Do not place log files or other heavy workloads on etcd drives.
+The following hard drive practices provide optimal etcd performance:
+
+* Use dedicated etcd drives. Avoid drives that communicate over the network, such as iSCSI. Do not place log files or other heavy workloads on etcd drives.
+* Prefer drives with low latency to support fast read and write operations.
+* Prefer high-bandwidth writes for faster compactions and defragmentation.
+* Prefer high-bandwidth reads for faster recovery from failures.
+* Use solid state drives as a minimum selection. Prefer NVMe drives for production environments.
+* Use server-grade hardware for increased reliability.
 
 [NOTE]
 ====