Restrict ingress to LAN and Tailscale

The router forwards internet traffic for git to the ingress NodePort, so
every hostname was reachable from the internet by its Host header.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
2026-10-18 14:23:11 +02:00
co-authored by Claude Opus 5.5
parent d126afb11b
commit 3a60751c2e
+6
View File
@@ -43,6 +43,12 @@ ingress:
clusterIssuer: letsencrypt-dns-cloudflare clusterIssuer: letsencrypt-dns-cloudflare
annotations: annotations:
nginx.ingress.kubernetes.io/proxy-body-size: 100m nginx.ingress.kubernetes.io/proxy-body-size: 100m
# LAN-only: home network + pods (incl. the Tailscale subnet router, 10.1.0.0/16), but
# NOT 192.168.2.218 - the router's internet forward (443 -> NodePort 30444, for git)
# arrives SNATed as the node's own IP. So internet clients that send this hostname
# get 403, while LAN clients reach the ingress directly on hostPort 443 with their
# real IP. Side effect: LAN access via :30444 is blocked too (use the URL without port).
nginx.ingress.kubernetes.io/whitelist-source-range: "192.168.2.0/25,192.168.2.128/26,192.168.2.192/28,192.168.2.208/29,192.168.2.216/31,192.168.2.219/32,192.168.2.220/30,192.168.2.224/27,10.1.0.0/16"
# StorageClass for the per-app config PVCs, empty = cluster default. # StorageClass for the per-app config PVCs, empty = cluster default.
storageClassName: "" storageClassName: ""