[stable/superset] Use the target port number instead of a name (helm#…

…7857) * [stable/superset] Use the target port number instead of a name Older (but still actual) versions of some Network Policy providers don't support named ports as a value of `targetPort` field in the Service spec. Changing it to the number shouldn't break the UX for existing installations. Signed-off-by: Mikhail Zholobov <[email protected]> * [stable/superset] Bump version Signed-off-by: Mikhail Zholobov <[email protected]>
agolo · Feb 15, 2019 · 0facbbc · 0facbbc
1 parent 38efafe
commit 0facbbc
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/stable/superset/Chart.yaml b/stable/superset/Chart.yaml
@@ -1,6 +1,6 @@
 description: Apache Superset (incubating) is a modern, enterprise-ready business intelligence web application
 name: superset
-version: 1.1.4
+version: 1.1.5
 appVersion: "0.28.1"
 keywords:
 - bi

diff --git a/stable/superset/templates/svc.yaml b/stable/superset/templates/svc.yaml
@@ -36,7 +36,7 @@ spec:
   ports:
     - name: http
       port: {{ .Values.service.port }}
-      targetPort: http
+      targetPort: 8088
       protocol: TCP
       {{- if (and (eq .Values.service.type "NodePort") (not (empty .Values.service.nodePort))) }}
       nodePort: {{.Values.service.nodePort}}