From 9c7b029d652adafa4036d24021d2765819c27e4c Mon Sep 17 00:00:00 2001 From: SmokyZone Date: Sun, 18 Oct 2026 14:23:11 +0200 Subject: [PATCH] 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 --- values.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/values.yaml b/values.yaml index 0c71327..8b49657 100644 --- a/values.yaml +++ b/values.yaml @@ -51,6 +51,12 @@ ingress: nginx.ingress.kubernetes.io/proxy-read-timeout: "3600" nginx.ingress.kubernetes.io/proxy-send-timeout: "3600" 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" # USB radios (Zigbee/Z-Wave sticks), e.g. /dev/serial/by-id/usb-...; needs privileged. devices: []