Fix broken port-forward instructions (#14039)

The pod listens on port 8088, not port 80. Also if you port-forward from the service then you don't have to bother getting the pod name.
apache · Apr 9, 2021 · 2c96c5b · 2c96c5b
1 parent a3b41e2
commit 2c96c5b
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/helm/superset/templates/NOTES.txt b/helm/superset/templates/NOTES.txt
@@ -31,7 +31,6 @@
   export SERVICE_IP=$(kubectl get svc --namespace {{ .Release.Namespace }} {{ template "superset.fullname" . }} -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
   echo http://$SERVICE_IP:{{ .Values.service.port }}
 {{- else if contains "ClusterIP" .Values.service.type }}
-  export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "app={{ template "superset.name" . }},release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}")
   echo "Visit http://127.0.0.1:8088 to use your application"
-  kubectl port-forward $POD_NAME 8088:80
+  kubectl port-forward service/superset 8088:8088 --namespace {{ .Release.Namespace }}
 {{- end }}