How mysticrenji/home-assistant-on-kubernetes works
Project type and purpose
• This is an infrastructure‐as‐code repository that provisions and runs a home‐automation full-stack system on a single-node K3s (lightweight Kubernetes) cluster, hosted on an ARM64 Nvidia Jetson Nano.
• Purpose: Deploy Home Assistant, BLE (Bluez) and Zigbee device adapters, a Cloudflare tunnel, networking components (MetalLB, Ingress‐Nginx), certificate management, and auxiliary services (Ansible-Semaphore, Plex) in containers.
File structure
• Top‐level:
• .github/ – CI workflows (build, test, renovate)
• home-automation/ – k8s manifests for core Home-Assistant, BLE service Dockerfile, configuration yamls (Deployment, ConfigMap, PVC, Ingress)
• sub-components/ – reusable k8s sub-charts/manifests for cert-manager, MetalLB, ingress-nginx, cloudflare-daemon, ansible-semaphore, kube-plex
• tests/ – sanity tests (nginx.yaml)
• Patterns:
• Microservices: each adapter and service runs in its own pod
• Kubernetes primitives: Deployments, ConfigMaps, PVCs, Ingress, custom namespaces
• Container builds (Dockerfile + app.js) for the BLE adapter
README for additional insights
• K3s runs with containerd on Jetson Nano (ARM64)
• Bluetooth Low Energy sensor integration via a custom Bluez service (app.js)
• Zigbee coordinator likewise runs in its own pod
• Home Assistant pod uses the official container image
• Cloudflare Daemon pod exposes services securely to the public Internet
• MetalLB handles bare-metal LoadBalancer IP assignment
• cert-manager issues TLS certificates via Helm
• Tailscale VPN stitches multiple ARM64 worker nodes into the cluster