increase initial liveness/readiness periods

It has been observed in windriver labs that initialization
times when downloading artifacts from onap nexus
repositories can be fairly long in duration.   When network is slow
readiness/liveness checks kicked in before the container is
fully initialized, therefore restarting the process until
it finds a window of time where initialization completes within
the time window.   This change increments those timers to
allow for complete initialization for slow installations.

Change-Id: I55f4a87e670020b8e6396a6a6a66f88345f300e7
Issue-ID: POLICY-879
Signed-off-by: Jorge Hernandez <jh1730@att.com>

diff --git a/kubernetes/policy/charts/drools/values.yaml b/kubernetes/policy/charts/drools/values.yaml
index 5a8e936..b469ce7 100644 (file)
--- a/kubernetes/policy/charts/drools/values.yaml
+++ b/kubernetes/policy/charts/drools/values.yaml
@@ -46,7 +46,7 @@ affinity: {}
 
 # probe configuration parameters
 liveness:
-  initialDelaySeconds: 60
+  initialDelaySeconds: 180
   periodSeconds: 10
   # necessary to disable liveness probe when setting breakpoints
   # in debugger so K8s doesn't restart unresponsive container