brandtkeller / home-assistant-helm

home-assistant-helm

Home Assistant

This chart is not maintained by the upstream project and any issues with the chart should be raised here

Using this repository as a location to house helm charts that I use for my deployments of Home Assistant and various services that integrate with Home Assistant.

Requirements

Home Assistant and zwave-js-ui do not allow declarative management as I have yet to find. When deploying a vanilla configuration there are some manual setup tasks currently.

• If you are deploying this behind a reverse proxy - you will need to add some configuration to your /config/configuration.yaml

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - x.x.x.x

- The trusted proxy address being the address of the reverse proxy traffic origination.

• If you are using the zwave-js-ui additions you will need to access the UI and Settings -> zwave -> and click save. This adds the zwave controller as couldn't be done via automation.

Dependencies

Try it out

git clone https://github.com/brandtkeller/home-assistant-helm.git

cd home-assitant-helm/charts/home-assistant

helm upgrade -i home-assistant -n ha --create-namespace ./chart/

home-assistant-helm's Issues

TODO: zwave2mqtt addon

Add a subchart for zwave JS UI in order to deploy it with home assistant when enabled.

TODO: data persistence

Need to define what data needs to be persisted

TODO: configuration process

Need to define how configuration to the primary configuration.yaml happens. Should this be a configmap that users would only modify through their helm installations or do we need to provide some other bootstrapping option and required persistence?

TODO: options for usb connectivity

How to enable privileged behavior like accessing USB devices from a pod in a secure manner.