Fix helm chart to allow configurable ingress pathType (#558)

charts/pulsar/templates/proxy-ingress.yaml

@@ -59,7 +59,7 @@ spec:
               servicePort: {{ .Values.proxy.ports.http }}
               {{- end }}
             {{- else }}
-            pathType: ImplementationSpecific
+            pathType: {{ .Values.proxy.ingress.pathType }}
             backend:
               service:
                 name: "{{ template "pulsar.fullname" . }}-{{ .Values.proxy.component }}"

charts/pulsar/templates/pulsar-manager-ingress.yaml

@@ -55,7 +55,7 @@ spec:
               serviceName: "{{ template "pulsar.fullname" . }}-{{ .Values.pulsar_manager.component }}"
               servicePort: {{ .Values.pulsar_manager.service.targetPort }}
             {{- else }}
-            pathType: ImplementationSpecific
+            pathType: {{ .Values.pulsar_manager.ingress.pathType }}
             backend:
               service:
                 name: "{{ template "pulsar.fullname" . }}-{{ .Values.pulsar_manager.component }}"

charts/pulsar/values.yaml

@@ -1297,6 +1297,7 @@ proxy:
 
     hostname: ""
     path: "/"
+    pathType: ImplementationSpecific
   ## Proxy PodDisruptionBudget
   ## templates/proxy-pdb.yaml
   ##
@@ -1523,6 +1524,7 @@ pulsar_manager:
 
     hostname: ""
     path: "/"
+    pathType: ImplementationSpecific
 
   ## On first install, the helm chart tries to reuse an existing secret with matching name by default
   ## if this should fail it uses the given username and password to create a new secret