fix: change limits and resources to take into account jvm startup bursts

kesnarrequested to merge
feat/scaling_fixes into develop

When a pod with JVM starts, it has some bursts in terms of cpu and memory. While the previous limits were mostly correct for the actual application, it didn't take into account those bursts.

Additionally the requested resources have been increased a bit in order to not trigger autoscale on startup. This is a temporary solution, in future we should investigate native builds to circumvent JVM altogether.

Edited by kesnar

Merge request reports

manifests/automationservice.yaml

+1 −1
Changes for manifests/automationservice.yaml: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -102,7 +102,7 @@ spec: 
              cpu: 50m

              memory: 512Mi

            limits:

              cpu: 500m

              cpu: 2000m

              memory: 2048Mi

---

apiVersion: autoscaling/v2

manifests/policyservice.yaml

+1 −1
Changes for manifests/policyservice.yaml: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -106,7 +106,7 @@ spec: 
              cpu: 50m

              memory: 512Mi

            limits:

              cpu: 500m

              cpu: 2000m

              memory: 2048Mi

---

apiVersion: autoscaling/v2