[stable/kubernetes-dashboard] Use the target port number instead of a name (#7548)

* [stable/kubernetes-dashboard] 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/kubernetes-dashboard] Bump chart version to 0.7.4

Signed-off-by: Mikhail Zholobov <legal90@gmail.com>
This commit is contained in:
Mikhail Zholobov
2018-10-22 09:44:57 -07:00
committed by k8s-ci-robot
parent fc4a83c05f
commit ae9e3f8ea4
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
name: kubernetes-dashboard
version: 0.7.3
version: 0.7.4
appVersion: 1.10.0
description: General-purpose web UI for Kubernetes clusters
keywords:
@@ -19,7 +19,7 @@ spec:
type: {{ .Values.service.type }}
ports:
- port: {{ .Values.service.externalPort }}
targetPort: https
targetPort: 8443
{{- if hasKey .Values.service "nodePort" }}
nodePort: {{ .Values.service.nodePort }}
{{- end }}