Merge pull request #36314 from libander/RHDEVDOCS-3095

RHDEVDOCS-3095: cluster logging updates

Author: abrennan89

modules/cluster-logging-logstore-limits.adoc

@@ -40,12 +40,14 @@ metadata:
 spec:
     logStore:
       type: "elasticsearch"
-      elasticsearch:
-        resources: <1>
-          requests:
+      elasticsearch:<1>
+        resources:
+          limits: <2>
+            memory: "32Gi"
+          requests: <3>
             cpu: "1"
-            memory: "64Gi"
-        proxy: <2>
+            memory: "16Gi"
+        proxy: <4>
           resources:
             limits:
               memory: 100Mi
@@ -54,21 +56,25 @@ spec:
 ----
 <1> Specify the CPU and memory requests for Elasticsearch as needed. If you leave these values blank,
 the OpenShift Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `16Gi` for the memory request and `1` for the CPU request.
-<2> Specify the CPU and memory requests for the Elasticsearch proxy as needed. If you leave these values blank, the OpenShift Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `256Mi` for the memory request and `100m` for the CPU request.
+<2> The maximum amount of resources a pod can use.
+<3> The minimum resources required to schedule a pod.
+<4> Specify the CPU and memory requests for the Elasticsearch proxy as needed. If you leave these values blank, the OpenShift Elasticsearch Operator sets default values that are sufficient for most deployments. The default values are `256Mi` for the memory request and `100m` for the CPU request.
 
-If you adjust the amount of Elasticsearch memory, you must change both the request value and the limit value.
+When adjusting the amount of Elasticsearch memory, the same value should be used for both `requests` and `limits`.
 
 For example:
 
 [source,yaml]
 ----
       resources:
-        limits:
+        limits: <1>
           memory: "32Gi"
-        requests:
+        requests: <2>
           cpu: "8"
           memory: "32Gi"
 ----
+<1> The maximum amount of the resource.
+<2> The minimum amount required.
 
 Kubernetes generally adheres the node configuration and does not allow Elasticsearch to use the specified limits.
 Setting the same value for the `requests` and `limits` ensures that Elasticsearch can use the memory you want, assuming the node has the memory available.