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:
- vault.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
-11
View File
@@ -41,14 +41,3 @@ server:
}
disable_mlock = true
service_registration "kubernetes" {}
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
ingressClassName: nginx
tls:
- secretName: letsencrypt-prod
hosts:
- vault.rubenhensen.nl
hosts:
- host: "vault.rubenhensen.nl"
+1 -1
View File
@@ -6,7 +6,7 @@ spec:
provider:
vault:
# In-cluster, so syncing secrets doesn't depend on Hetzner or the home
# internet connection. Plain HTTP, like the ingress → Vault hop.
# internet connection. Plain HTTP, like the Gateway → Vault hop.
server: "http://vault-active.vault.svc:8200"
path: "kv"
# Version is the Vault KV secret engine version.