Skaronator commented on pull request #54:
URL: https://github.com/apache/pulsar-helm-chart/pull/54#issuecomment-678109920


   I think it would be much better to use the offical helm approach for 
defining ingress. The host is basically a array which can be empty (eg. what 
you want).
   
   You can do `helm create test` and then look at the created ingress at 
test/template/ingress.yaml. It looks like that:
   
   ```
   {{- if .Values.ingress.enabled -}}
   {{- $fullName := include "test.fullname" . -}}
   {{- $svcPort := .Values.service.port -}}
   {{- if semverCompare ">=1.14-0" .Capabilities.KubeVersion.GitVersion -}}
   apiVersion: networking.k8s.io/v1beta1
   {{- else -}}
   apiVersion: extensions/v1beta1
   {{- end }}
   kind: Ingress
   metadata:
     name: {{ $fullName }}
     labels:
       {{- include "test.labels" . | nindent 4 }}
     {{- with .Values.ingress.annotations }}
     annotations:
       {{- toYaml . | nindent 4 }}
     {{- end }}
   spec:
     {{- if .Values.ingress.tls }}
     tls:
       {{- range .Values.ingress.tls }}
       - hosts:
           {{- range .hosts }}
           - {{ . | quote }}
           {{- end }}
         secretName: {{ .secretName }}
       {{- end }}
     {{- end }}
     rules:
       {{- range .Values.ingress.hosts }}
       - host: {{ .host | quote }}
         http:
           paths:
             {{- range .paths }}
             - path: {{ . }}
               backend:
                 serviceName: {{ $fullName }}
                 servicePort: {{ $svcPort }}
             {{- end }}
       {{- end }}
     {{- end }}
   ```
   And the values.yaml looks like that:
   
   ```
   ingress:
     enabled: false
     annotations: {}
       # kubernetes.io/ingress.class: nginx
       # kubernetes.io/tls-acme: "true"
     hosts:
       - host: chart-example.local
         paths: []
     tls: []
     #  - secretName: chart-example-tls
     #    hosts:
     #      - chart-example.local
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to