Skip to content

v0.6.0

Choose a tag to compare

View all tags
@przemekhys przemekhys released this 09 Mar 20:50
· 323 commits to main since this release
v0.6.0
960ab4b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[0.6.0] - 2026-03-09

Added

  • HomeAssistantAutomation / Scene / Script: individual management via HA REST API — each CR is now managed individually via POST /api/config/{type}/config/{id} (create/update) and DELETE /api/config/{type}/config/{id} (removal). Home Assistant writes directly to automations.yaml / scenes.yaml / scripts.yaml on the PVC. The old ConfigMap aggregation approach (<ha-name>-automations, <ha-name>-scenes, <ha-name>-scripts) has been removed.
    • Status condition ReloadReady reflects the last API call result
    • When the bootstrap token is not yet available, the controller requeues with backoff (30s) and sets ReasonTokenNotAvailable
    • Deletion via finalizer calls DELETE to HA API (best-effort — continues even when HA is unavailable)

Migration (v0.5.x → v0.6.0)

Note for existing deployments: when upgrading from v0.5.x to v0.6.0, the operator will automatically remove the old aggregation ConfigMaps (<ha-name>-automations, <ha-name>-scenes, <ha-name>-scripts) and their volume mounts from the Home Assistant StatefulSet. The HA pod will be restarted once during this migration. After restart, existing automations/scenes/scripts CRs will be re-synced to HA via the REST API.

Assets 2
Loading