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

This commit is contained in:
Raúl Sánchez 2024-12-11 16:21:03 +01:00 committed by GitHub
parent 05c78df4c5
commit df9284dc97
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 4 additions and 2 deletions

View File

@ -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 }}"

View File

@ -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 }}"

View File

@ -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