1
0
Fork 0
Commit Graph

3 Commits (8c605d0f9fae8b2a6f42c64974342b6c53da03da)

Author SHA1 Message Date
Dustin a7eac14d39 home-assistant: Deploy Home Assistant
This commit adds resources for deploying the Home Assistant ecosystem
inside Kubernetes.  Home Assistant itself, as well as Mosquitto, are
just normal Pods, managed by StatefulSets, that can run anywhere.
ZWaveJS2MQTT and Zigbee2MQTT, on the other hand, have to run on a
special node (a Raspberry Pi), where the respective controllers are
attached.

The Home Assistant UI is exposed externally via an Ingress resource.
The MQTT broker is also exposed externally, using the TCP proxy feature
of *ingress-nginx*.  Additionally, the Zigbee2MQTT and ZWaveJS2MQTT
control panels are exposed via Ingress resources, but these are
protected by Authelia.
2023-07-24 17:53:58 -05:00
Dustin 7bd7dc7b18 ingress: Show how to import cert as secret 2022-08-23 21:20:47 -05:00
Dustin 30cbc568d0 ingress: Add manifest for ingress-nginx
This manifest deploys the *ingress-nginx* controller, which is
responsible for handing traffic from clients outside the cluster and
routing it to the proper pods.  I am using host network mode here to
avoid having to have another proxy in front of the ingress controller,
which would be required in NodePort mode.

I looked at MetalLB briefly, but decided to avoid it for now.  As with
everything else in the Kubernetes world, it seems massively complex.
2022-07-31 00:57:12 -05:00