Increase recommended k8s resource requests / limits (#29457)

Changes the recommended k8s resource limits / requests to be more suitable for synthetics. (cherry picked from commit b462430)
elastic · Jan 24, 2022 · ba4e29c · ba4e29c
1 parent c6bec41
commit ba4e29c
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 6 deletions.
diff --git a/deploy/kubernetes/heartbeat-kubernetes.yaml b/deploy/kubernetes/heartbeat-kubernetes.yaml
@@ -100,10 +100,14 @@ spec:
           runAsUser: 0
         resources:
           limits:
-            memory: 200Mi
+            memory: 1536mi
           requests:
-            cpu: 100m
-            memory: 100Mi
+            # for synthetics, 2 full cores is a good starting point for relatively consistent perform of a single concurrent check
+            # For lightweight checks as low as 100m is fine
+            cpu: 2000m 
+            # A high value like this is encouraged for browser based monitors. 
+            # Lightweight checks use substantially less, even 128Mi is fine for those.
+            memory: 1536Mi 
         volumeMounts:
         - name: config
           mountPath: /etc/heartbeat.yml

diff --git a/deploy/kubernetes/heartbeat/heartbeat-deployment.yaml b/deploy/kubernetes/heartbeat/heartbeat-deployment.yaml
@@ -46,10 +46,14 @@ spec:
           runAsUser: 0
         resources:
           limits:
-            memory: 200Mi
+            memory: 1536mi
           requests:
-            cpu: 100m
-            memory: 100Mi
+            # for synthetics, 2 full cores is a good starting point for relatively consistent perform of a single concurrent check
+            # For lightweight checks as low as 100m is fine
+            cpu: 2000m 
+            # A high value like this is encouraged for browser based monitors. 
+            # Lightweight checks use substantially less, even 128Mi is fine for those.
+            memory: 1536Mi 
         volumeMounts:
         - name: config
           mountPath: /etc/heartbeat.yml