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]>
68 lines
2.7 KiB
YAML
68 lines
2.7 KiB
YAML
## Values for the Home Assistant chart.
|
|
|
|
image:
|
|
repository: ghcr.io/home-assistant/home-assistant
|
|
tag: "2026.10.2"
|
|
|
|
tz: Europe/Berlin
|
|
|
|
# Run in the node's network namespace. Required for LAN discovery (mDNS/SSDP:
|
|
# Chromecast, Hue, Sonos, HomeKit, ...), which does not cross the pod network.
|
|
# Side effect: port 8123 (plain HTTP) is also open on the node's LAN IP.
|
|
hostNetwork: true
|
|
|
|
port: 8123
|
|
|
|
persistence:
|
|
# /config: configuration.yaml, .storage (users, integrations), SQLite recorder DB.
|
|
size: 5Gi
|
|
storageClassName: ""
|
|
|
|
# Lets HA accept requests from ingress-nginx (pod network 10.1.0.0/16); without it HA
|
|
# answers 400 Bad Request to proxied requests. Since 2026.10 HA keeps the HTTP settings
|
|
# in /config/.storage/http (UI-managed); an `http:` block in configuration.yaml is only
|
|
# imported as an unconfirmed trial and reverted after 5 minutes. So the chart seeds the
|
|
# store directly - on first start only, never overwriting an existing one.
|
|
trustedProxies:
|
|
- 10.1.0.0/16
|
|
- 127.0.0.1/32
|
|
|
|
# Written to /config/configuration.yaml on first start only (when the file does not
|
|
# exist yet). Afterwards the file belongs to you; the chart never overwrites it.
|
|
seedConfiguration: |
|
|
# Loads the default set of integrations. Do not remove.
|
|
default_config:
|
|
|
|
frontend:
|
|
themes: !include_dir_merge_named themes
|
|
|
|
automation: !include automations.yaml
|
|
script: !include scripts.yaml
|
|
scene: !include scenes.yaml
|
|
|
|
ingress:
|
|
enabled: true
|
|
className: nginx
|
|
# https://homeassistant.smokyzone.de (ingress-nginx hostPort 443; NodePort :30444 also works)
|
|
host: homeassistant.smokyzone.de
|
|
clusterIssuer: letsencrypt-dns-cloudflare
|
|
annotations:
|
|
# Websocket connection of the frontend / companion app stays open.
|
|
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: []
|
|
privileged: false
|
|
|
|
resources:
|
|
requests: {cpu: 100m, memory: 512Mi}
|
|
limits: {cpu: "2", memory: 2Gi}
|