From 4aff7f0653121f7114d42eec3d09531ac13c1e27 Mon Sep 17 00:00:00 2001
From: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Date: Thu, 14 May 2020 13:21:06 +0200
Subject: [PATCH] [AAF] Augment CPU limit to locate

AAF locate may be long to start because of too small CPU limits.
Augmenting them in order to have a more reliable behavior

Issue-ID: OOM-2411
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Iefcd79ee66be56570a5df83111cbb6559346371e
---
 kubernetes/aaf/charts/aaf-locate/values.yaml | 30 ++++++++++++++--------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/kubernetes/aaf/charts/aaf-locate/values.yaml b/kubernetes/aaf/charts/aaf-locate/values.yaml
index 47b2f205e5..01a5ab158a 100644
--- a/kubernetes/aaf/charts/aaf-locate/values.yaml
+++ b/kubernetes/aaf/charts/aaf-locate/values.yaml
@@ -62,18 +62,18 @@ ingress:
 
 # Configure resource requests and limits
 resources:
-  small:
-    limits:
-      cpu: 100m
-      memory: 320Mi
-    requests:
-      cpu: 1m
-      memory: 210Mi
-  large:
-    limits:
-      cpu: 400m
-      memory: 1Gi
-    requests:
-      cpu: 40m
-      memory: 500Mi
-  unlimited: {}
+ small:
+   limits:
+     cpu: 500m
+     memory: 320Mi
+   requests:
+     cpu: 1m
+     memory: 210Mi
+ large:
+   limits:
+     cpu: 400m
+     memory: 1Gi
+   requests:
+     cpu: 40m
+     memory: 500Mi
+ unlimited: {}
-- 
2.16.6