From: Dominic Lunanuova <dgl@research.att.com>
Date: Wed, 8 Apr 2020 21:16:30 +0000 (+0000)
Subject: Workaround for cert expiration
X-Git-Tag: 5.0.2-ONAP~13^2
X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=refs%2Fchanges%2F67%2F105567%2F4;p=oom.git

Workaround for cert expiration

Issue-ID: DMAAP-1424
Signed-off-by: Dominic Lunanuova <dgl@research.att.com>
Change-Id: I27f0302f00bfbdce6f8c7d778018ee4dcdea0958
---

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