Replace the Ingresses with Certificate resources

ingress-nginx is gone and every app is served by the Envoy Gateway. The certificates were created by cert-manager's ingress-shim and are owned by the Ingresses, so each app now declares its Certificate itself, with the same name, secret and usages, so nothing gets reissued. gateway-shim can't take over because the certificates live in the app namespaces.

immich drops mbg.hensen.io, which has no route, so that one certificate is reissued through the Gateway's HTTP-01 solver.

Also removes the Longhorn test-port redirect URI and updates comments that still described nginx.
This commit is contained in:
Ruben Hensen committed 2026-10-23 21:20:25 +02:00
1 parent 48f5c7d894
commit 1f04831a97
38 files changed
+239 -371

No files matched your search

+16
View File
@@ -0,0 +1,16 @@
# The TLS certificate the Gateway serves for this app (see httproute.yaml).
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: letsencrypt-prod
spec:
secretName: letsencrypt-prod
dnsNames:
- ha.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
-41
View File
@@ -1,41 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: home-assistant-ingress
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "false"
# nginx.ingress.kubernetes.io/enable-cors: "true"
# type of authentication
# nginx.ingress.kubernetes.io/auth-type: basic
# name of the secret that contains the user/password definitions
# nginx.ingress.kubernetes.io/auth-secret: longhorn-basic-auth
# message to display with an appropriate context why the authentication is required
# nginx.ingress.kubernetes.io/auth-realm: 'Authentication Required '
# nginx.ingress.kubernetes.io/cors-allow-origin: "http://localhost:3000/"
# nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, OPTIONS, DELETE"
# If you encounter a redirect loop or are getting a 307 response code
# then you need to force the nginx ingress to connect to the backend using HTTPS.
#
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
# namespace: ente-photos
spec:
ingressClassName: nginx
rules:
- host: ha.rubenhensen.nl
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: home-assistant-external
port:
number: 8123
tls:
- secretName: letsencrypt-prod
hosts:
- ha.rubenhensen.nl
+3 -3
View File
@@ -1,6 +1,6 @@
# Home Assistant runs outside the cluster on 192.168.1.202. ingress-nginx
# 1.13 resolves an ExternalName as a DNS name and fails on a bare IP, so
# point a selector-less Service at it with a hand-written EndpointSlice.
# Home Assistant runs outside the cluster on 192.168.1.202. An ExternalName
# Service needs a DNS name, not a bare IP, so point a selector-less Service
# at it with a hand-written EndpointSlice.
apiVersion: v1
kind: Service
metadata: