chore(hass): rename values to secret to encrypt token and add README

2026-05-17 10:52:11 +02:00
parent e90ad7b4df
commit b82ff8a09f
3 changed files with 27 additions and 229 deletions
@@ -0,0 +1,27 @@
+# Home Assistant
+
+Deployment for Home Assistant via the `pajikos` Helm chart.
+
+## Deployment
+
+1. Ensure the Helm repository is added and updated:
+```bash
+helm repo add pajikos https://pajikos.github.io/home-assistant-helm-chart/
+helm repo update
+```
+
+2. Apply the raw secrets (if they haven't been applied yet):
+```bash
+kubectl apply -f hass-code-auth.secret.yml
+```
+
+3. Upgrade/Install the Helm release:
+```bash
+helm upgrade --install home-assistant pajikos/home-assistant -n home-assistant -f home-assistant.secret.yaml
+```
+
+## Architecture & Configuration
+This setup perfectly balances **Infrastructure as Code (IaC)** with **Dynamic UI Configuration**:
+- **Core Settings:** Network proxies, InfluxDB tokens, and Ingress routing are strictly enforced via `home-assistant.secret.yaml`.
+- **Dynamic Config:** The helm chart utilizes an init-script to inject `!include` directives for `automations.yaml`, `scripts.yaml`, and `scenes.yaml` into the main config. This allows the Home Assistant UI to write dynamic automations without violating the IaC principles!
+- **Code Server Addon:** For advanced manual tweaks, a VS Code instance (`hass-coder.moritzgraf.de`) runs alongside the pod, allowing direct manipulation of the `/config` directory.