4.6.0 policy-handler active-passive

[oom.git] / kubernetes / dcaegen2 / charts / dcae-bootstrap / resources / inputs / k8s-policy_handler-inputs.yaml

diff --git a/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml b/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
index 50ac16f..9cd37b5 100644 (file)
--- a/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
+++ b/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
@@ -31,6 +31,12 @@ application_config:
     policy_retry_count : 5
     policy_retry_sleep : 5
 
+    # mode of operation for the policy-handler
+    # either active or passive
+    # in passive mode the policy-hanlder will not listen to
+    #                 and will not bring the policy-updates from policy-engine
+    mode_of_operation : "active"
+
     # config of automatic catch_up for resiliency
     catch_up :
         # interval in seconds on how often to call automatic catch_up
@@ -77,7 +83,7 @@ application_config:
         # optional timeout_in_secs specifies the timeout for the http requests
         timeout_in_secs: 60
         # optional ws_ping_interval_in_secs specifies the ping interval for the web-socket connection
-        ws_ping_interval_in_secs: 180
+        ws_ping_interval_in_secs: 30
     # deploy_handler config
     #    changed from string "deployment_handler" in 2.3.1 to structure in 2.4.0
     deploy_handler :