[home-assistant] included esphome fails to start on multi-node clusters about charts HOT 6 CLOSED

It would be interesting to find a way to mount the Kube secret as secrets.yaml in a place that hass will recognize it.

from charts.

@bjw-s -- do you think we could leverage some of the secrets work we were discussing for Hass here too?

from charts.

By the looks of it you could manage the secrets file from a Kubernetes Secret with something like the following values in values.yaml. You would have a small bit of duplication in the values file though:

esphome:
  extraVolumes:
    - name: hass-secrets
      secret:
        secretName: <pre-existing secret name goes here>
  extraVolumeMounts:
     - name: hass-secrets
       mountPath: /config/secrets.yaml
       subPath: secrets.yaml

extraVolumes:
  - name: hass-secrets
    secret:
      secretName: <pre-existing secret name goes here>

extraVolumeMounts:
   - name: hass-secrets
     mountPath: /config/secrets.yaml
     subPath: secrets.yaml

from charts.

Someone made a comment somewhere that suggested we merge the esphome chart into homeassistant and make it a single pod like vscode is today. THoughts?

from charts.

So, had a chat with maui in discord and I'm not certain it makes sense to merge esphome with hass. The only real value is that the secrets.yaml file becomes accessible to esphome devices. I'm not certain there's a ton of value there outside of MQTT creds that outweighs just managing them separately.

from charts.

The esphome subchart was removed in #212, so closing this issue.

from charts.