[stable/superset] Use the target port number instead of a name (#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 <legal90@gmail.com>

* [stable/superset] Bump version

Signed-off-by: Mikhail Zholobov <legal90@gmail.com>
This commit is contained in:
Mikhail Zholobov
2019-02-15 05:52:32 -08:00
committed by Kubernetes Prow Robot
parent 38efafea7d
commit 0facbbcf21
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -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
+1 -1
View File
@@ -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}}