summaryrefslogtreecommitdiffstats
path: root/kubernetes/dmaap/components/dmaap-bc/templates
diff options
context:
space:
mode:
Diffstat (limited to 'kubernetes/dmaap/components/dmaap-bc/templates')
-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