Post

Home Assistant

Home Assistant

Home Assistant

Purpose

Home Assistant is the home automation hub for the homelab. Runs as a single Deployment in the default namespace of the k3s cluster, pinned to a specific node.

Deployment

ItemValue
Namespacedefault
Imagehomeassistant/home-assistant:2026.8
Replicas1 (strategy: Recreate)
Nodepinned to cm4-left via nodeSelector
NetworkinghostNetwork: true, dnsPolicy: ClusterFirstWithHostNet (needed for device discovery, e.g. mDNS/SSDP)
Container port8123
Resourcesrequests 200m/512Mi, limits 1500m/1536Mi
StoragePVC homeassistant-data, 10Gi, storageClassName: longhorn/config
Reloaderreloader.stakater.com/auto: "true"

Startup/readiness/liveness probes all hit /manifest.json on port 8123. The startupProbe allows up to 10 minutes (failureThreshold: 60, periodSeconds: 10) for Home Assistant’s first-boot integration setup.

Ingress

Traefik IngressRoute, TLS via the shared local-example-com-tls wildcard cert, routes both the bare domain and the dedicated subdomain to the homeassistant Service on port 8123:

  • iot-proxmox.net / www.iot-proxmox.net
  • homeassistant.prod-k3s.iot-proxmox.net / www.homeassistant.prod-k3s.iot-proxmox.net (with default-headers middleware)

Notes

hostNetwork: true is a deliberate exception here — unlike other apps in this cluster, Home Assistant needs to see the LAN directly for local device discovery, which a pod’s normal cluster-networked namespace would block.

This post is licensed under CC BY 4.0 by the author.