Merge pull request #27359 from ahardin-rh/4-6-tested-cluster-max-style

4.6 tested cluster maximums table style updates

Author: ahardin-rh

modules/openshift-cluster-maximums.adoc

@@ -9,7 +9,7 @@
 |===
 | Maximum type |4.1 and 4.2 tested maximum |4.3 tested maximum |4.4 tested maximum |4.5 tested maximum |4.6 tested maximum
 
-| Number of Nodes
+| Number of nodes
 | 2,000
 | 2,000
 | 250
@@ -37,49 +37,49 @@
 | There is no default value.
 | There is no default value.
 
-| Number of Namespaces ^[2]^
+| Number of namespaces ^[2]^
 | 10,000
 | 10,000
 | 10,000
 | 10,000
 | 10,000
 
-| Number of Builds
+| Number of builds
 | 10,000 (Default pod RAM 512 Mi) - Pipeline Strategy
 | 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
 | 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
 | 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
 | 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
 
-| Number of pods per Namespace ^[3]^
+| Number of pods per namespace ^[3]^
 | 25,000
 | 25,000
 | 25,000
 | 25,000
 | 25,000
 
-| Number of Services ^[4]^
+| Number of services ^[4]^
 | 10,000
 | 10,000
 | 10,000
 | 10,000
 | 10,000
 
-| Number of Services per Namespace
+| Number of services per namespace
 | 5,000
 | 5,000
 | 5,000
 | 5,000
 | 5,000
 
-| Number of Back-ends per Service
+| Number of back ends per service
 | 5,000
 | 5,000
 | 5,000
 | 5,000
 | 5,000
 
-| Number of Deployments per Namespace ^[3]^
+| Number of deployments per namespace ^[3]^
 | 2,000
 | 2,000
 | 2,000
@@ -92,7 +92,7 @@
 1. The pod count displayed here is the number of test pods. The actual number of pods depends on the application’s memory, CPU, and storage requirements.
 2. When there are a large number of active projects, etcd might suffer from poor performance if the keyspace grows excessively large and exceeds the space quota. Periodic maintenance of etcd, including defragmentaion, is highly recommended to free etcd storage.
 3. There are a number of control loops in the system that must iterate over all objects in a given namespace as a reaction to some changes in state. Having a large number of objects of a given type in a single namespace can make those loops expensive and slow down processing given state changes. The limit assumes that the system has enough CPU, memory, and disk to satisfy the application requirements.
-4. Each service port and each service back-end has a corresponding entry in iptables. The number of back-ends of a given service impact the size of the endpoints objects, which impacts the size of data that is being sent all over the system.
+4. Each service port and each service back end has a corresponding entry in iptables. The number of back ends of a given service impact the size of the endpoints objects, which impacts the size of data that is being sent all over the system.
 --
 
 In {product-title} {product-version}, half of a CPU core (500 millicore) is reserved by the system compared to {product-title} 3.11 and previous versions.