feat: add support for ingress multiplath

Author: jlpedrosaSnoo

charts/zigbee2mqtt/templates/ingress.yaml

@@ -26,31 +26,20 @@ spec:
     {{- tpl (toYaml .) $ | nindent 4 }}
   {{- end }}
   rules:
-  {{- if .Values.ingress.hosts  }}
   {{- range .Values.ingress.hosts }}
-    - host: {{ tpl . $ | quote }}
+    - host: {{ .host | quote }}
       http:
         paths:
-          - path: {{ $ingressPath }}
-            pathType: {{ $ingressPathType }}
+          {{- range .paths }}
+          - path: {{ .path }}
+           {{- if .pathType }}
+            pathType: {{ .pathType }}
+            {{- end }}
             backend:
               service:
                 name: {{ $fullName }}
                 port:
                   number: {{ $servicePort }}
+          {{- end }}
   {{- end }}
-  {{- else }}
-    - http:
-        paths:
-          - backend:
-              service:
-                name: {{ $fullName }}
-                port:
-                  number: {{ $servicePort }}
-            {{- with $ingressPath }}
-            path: {{ . }}
-            {{- end }}
-            pathType: {{ $ingressPathType }}
-
-  {{- end -}}
 {{- end }}

charts/zigbee2mqtt/values.yaml

@@ -178,24 +178,30 @@ zigbee2mqtt:
     # In case you are having issues try `200`.
     # For more information see https://github.com/Koenkk/zigbee2mqtt/issues/4884
     adapter_delay: 0
+# -- Ingress configuration. Zigbee2mqtt does use webssockets, which is not part of the Ingress standart settings.
+# most of the popular ingresses supports them through annotations. Please check https://www.zigbee2mqtt.io/guide/installation/08_kubernetes.html
+# for examples.
 ingress:
   # -- When enabled a new Ingress will be created
   enabled: false
-  # The ingress class name for the ingress
+  # -- The ingress class name for the ingress
   ingressClassName: contour
-  # Additional labels for the ingres
+  # -- Additional labels for the ingres
   labels: {}
-  # URL in which the ingress will be accepting requests for zigbee2mqtt
-  path: /
-  # Ingress implementation specific (potentially) for most use cases Prefix should be ok
+  # -- Ingress implementation specific (potentially) for most use cases Prefix should be ok
   pathType: Prefix
   # Additional annotations for the ingress. ExternalDNS, and CertManager are tipically integrated here
-  annotations: {}
-  # configuration for tls service (ig any)
+  annotations: { }
+  # -- list of hosts that should be allowed for the zigbee2mqtt service
+  hosts:
+    - host: chart-example.local
+      paths:
+        - path: /
+          pathType: ImplementationSpecific
+        - path: /api
+          pathType: ImplementationSpecific
+  # -- configuration for tls service (ig any)
   tls:
     - secretName: some-tls-secret
       hosts:
-        - yourdomain.com
-  # list of hosts that should be allowed for the zigbee2mqtt service
-  hosts:
-    - yourdomain.com
+        - yourdomain.com