aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/dmaap
diff options
context:
space:
mode:
authorDominic Lunanuova <dgl@research.att.com>2020-04-08 21:16:30 +0000
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-05-19 13:46:39 +0000
commit59006cf1a7051d80de0f949b31c4d8131978e1ee (patch)
treebb07a886b58629a2c5d8269f6cfdb5defe4dcb40 /kubernetes/dmaap
parent5a2429acb1a73119ffe25652e1eb3cce0c6f93f8 (diff)
Workaround for cert expiration
Issue-ID: DMAAP-1424 Signed-off-by: Dominic Lunanuova <dgl@research.att.com> Change-Id: I27f0302f00bfbdce6f8c7d778018ee4dcdea0958
Diffstat (limited to 'kubernetes/dmaap')
-rw-r--r--kubernetes/dmaap/components/dmaap-bc/templates/post-install-job.yaml11
1 files changed, 10 insertions, 1 deletions
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