From: Krzysztof Opasiak <k.opasiak@samsung.com>
Date: Tue, 19 May 2020 22:03:03 +0000 (+0000)
Subject: Merge "[AAI|ROBOT] track latest commits on submodules" into elalto
X-Git-Tag: 5.0.2-ONAP~12
X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=bd69b018a250990a6923b0d74c7a573d2e3e6b2c;hp=ae635d4fb2c346ea0e78c6ac1ee7cd62b419e24c;p=oom.git

Merge "[AAI|ROBOT] track latest commits on submodules" into elalto
---

diff --git a/kubernetes/dmaap/components/dmaap-bc/templates/post-install-job.yaml b/kubernetes/dmaap/components/dmaap-bc/templates/post-install-job.yaml
index 52c5566061..df823b5cd7 100644
--- a/kubernetes/dmaap/components/dmaap-bc/templates/post-install-job.yaml
+++ b/kubernetes/dmaap/components/dmaap-bc/templates/post-install-job.yaml
@@ -32,8 +32,17 @@ spec:
         env:
         - name: DELAY
           value: "0"
+# hack explanation:
+# since the dmaap-bc SSL certificate is expired in this release, we
+# pass the -k flag to ignore the cert check error.
+# AFAIK, this post-install script is the only client which actually
+# uses https (against dmaap-bc API) in El Alto Release.
+# So, this workaround is the easiest way out for me.
+# Also note that the only reason to even deploy dmaap-bc is if you
+# need authenticated topics in message-router, or a feed in data-router.
+# If that is not your case, then don't even deploy dmaap-bc.
         - name: PROTO
-          value: "https"
+          value: "-k https"
         - name: PORT
           value: "8443"
         - name: REQUESTID