aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes
diff options
context:
space:
mode:
authorMandeep Khinda <mandeep.khinda@amdocs.com>2018-09-21 03:59:17 +0000
committerMandeep Khinda <mandeep.khinda@amdocs.com>2018-09-21 04:01:16 +0000
commitcef0e3c71445df18f2e8f0ef94342caac2be81b1 (patch)
treec773cb2979edfc59e9f576a57da885d20c4deba0 /kubernetes
parent885cc2df865888d8f68b218e8fe30f40d62b4fde (diff)
fixing vid startup issue after resource limit
The resource allocation is sufficient, however the pod takes longer to start and was being killed by the liveness probe. Increased probe delay to 2min and cpu core resources Issue-ID: OOM-1167 Change-Id: Ic2cdf2bd4a275d6f23ccaa7b8938ad6e1c1b5a4a Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Diffstat (limited to 'kubernetes')
-rw-r--r--kubernetes/vid/values.yaml10
1 files changed, 5 insertions, 5 deletions
diff --git a/kubernetes/vid/values.yaml b/kubernetes/vid/values.yaml
index 1c85af89a7..4b0f38c4b8 100644
--- a/kubernetes/vid/values.yaml
+++ b/kubernetes/vid/values.yaml
@@ -66,7 +66,7 @@ affinity: {}
# probe configuration parameters
liveness:
- initialDelaySeconds: 10
+ initialDelaySeconds: 120
periodSeconds: 10
# necessary to disable liveness probe when setting breakpoints
# in debugger so K8s doesn't restart unresponsive container
@@ -97,15 +97,15 @@ flavor: small
resources:
small:
limits:
- cpu: 20m
+ cpu: 200m
memory: 2Gi
requests:
- cpu: 10m
+ cpu: 100m
memory: 1Gi
large:
limits:
- cpu: 40m
+ cpu: 400m
memory: 4Gi
requests:
- cpu: 20
+ cpu: 200m
memory: 2Gi \ No newline at end of file