Add immich LAN ingress and remove unsupported helm config

- Created custom ingress-lan.yaml for immich.f3s.lan.buetow.org with TLS
- Removed unsupported 'lan' ingress config from ArgoCD app values
- The Immich Helm chart doesn't support multiple named ingresses,
  so we create the LAN ingress as a custom resource instead

This aligns immich with other services that have both regular and
LAN ingress endpoints.

1 files changed, 26 insertions, 0 deletions

diff --git a/f3s/immich/helm-chart/templates/ingress-lan.yaml b/f3s/immich/helm-chart/templates/ingress-lan.yaml
new file mode 100644
index 0000000..8309b3c
--- /dev/null
+++ b/f3s/immich/helm-chart/templates/ingress-lan.yaml
@@ -0,0 +1,26 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: immich-server-lan
+  namespace: services
+  annotations:
+    spec.ingressClassName: traefik
+    traefik.ingress.kubernetes.io/router.entrypoints: web,websecure
+    traefik.ingress.kubernetes.io/router.middlewares: services-immich-body-size@kubernetescrd
+spec:
+  ingressClassName: traefik
+  tls:
+    - hosts:
+        - immich.f3s.lan.buetow.org
+      secretName: f3s-lan-tls
+  rules:
+    - host: immich.f3s.lan.buetow.org
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: immich-server
+                port:
+                  number: 2283