feat: make it possible to use ingress and service-type "LoadBalancer"…

… at the same time

When service type is "LoadBalancer" and ingress is enabled, a second service is deployed. There are two services at that point. One for the ingress and one for the LoadBalancer.

templates/ingress.yaml

@@ -49,7 +49,7 @@ spec:
             backend:
               {{- if semverCompare ">=1.19-0" $.Capabilities.KubeVersion.GitVersion }}
               service:
-                name: {{ $fullName }}
+                name: {{ $fullName }}-headless
                 port:
                   number: {{ $svcPort }}
               {{- else }}

templates/service-headless.yaml

@@ -0,0 +1,19 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: {{ include "gotify.fullname" . }}-headless
+  labels:
+    {{- include "gotify.labels" . | nindent 4 }}
+spec:
+  {{- if eq .Values.service.type "LoadBalancer" }}
+  type: ClusterIP
+  {{- else }}
+  type: {{ .Values.service.type }}
+  {{- end }}
+  ports:
+    - port: {{ .Values.service.port }}
+      targetPort: http
+      protocol: TCP
+      name: http
+  selector:
+    {{- include "gotify.selectorLabels" . | nindent 4 }}

templates/service.yaml

@@ -1,15 +1,17 @@
+{{- if and (eq .Values.service.type "LoadBalancer") (.Values.ingress.enabled) }}
 apiVersion: v1
 kind: Service
 metadata:
   name: {{ include "gotify.fullname" . }}
   labels:
     {{- include "gotify.labels" . | nindent 4 }}
 spec:
-  type: {{ .Values.service.type }}
+  type: LoadBalancer
   ports:
     - port: {{ .Values.service.port }}
       targetPort: http
       protocol: TCP
       name: http
   selector:
     {{- include "gotify.selectorLabels" . | nindent 4 }}
+{{- end }}