[recoverability][high] home-assistant namespace: 9 PVCs have no backup #192

Closed
opened 2026-07-14 09:47:02 +00:00 by claude-bot · 1 comment
Member

Finding

The home-assistant namespace has no Velero schedule; 9 PVCs are uncovered, including home-assistant-config (20Gi, holds .storage entity registry + recorder DB + secrets.yaml), esphome-data, shelly-manager-data, matter-server-data, otbr-data, whisper-data, speech-to-phrase-models/train, zone-configurator-config.

Verified

No schedule for home-assistant in velero-schedules.yaml; PVCs enumerated from kubernetes/apps/home-assistant/*. The git config-sync sidecar only covers YAML config, not .storage/recorder state.

Impact

Loss of these volumes loses HA entity/automation state with no backup.

Fix

Add a Velero schedule for home-assistant (at minimum home-assistant-config).


Automated security review 2026-07-14. Verified against manifests.

## Finding The home-assistant namespace has no Velero schedule; 9 PVCs are uncovered, including home-assistant-config (20Gi, holds .storage entity registry + recorder DB + secrets.yaml), esphome-data, shelly-manager-data, matter-server-data, otbr-data, whisper-data, speech-to-phrase-models/train, zone-configurator-config. ## Verified No schedule for home-assistant in velero-schedules.yaml; PVCs enumerated from kubernetes/apps/home-assistant/*. The git config-sync sidecar only covers YAML config, not .storage/recorder state. ## Impact Loss of these volumes loses HA entity/automation state with no backup. ## Fix Add a Velero schedule for home-assistant (at minimum home-assistant-config). --- _Automated security review 2026-07-14. Verified against manifests._
Author
Member

Verified against origin/master (07c93e4): confirmed. home-assistant, esphome, shelly-manager, matter-server, otbr, whisper, speech-to-phrase, and zone-configurator all deploy into the home-assistant namespace (matter-server/otbr/whisper/speech-to-phrase/zone-configurator each set namespace: home-assistant in their own kubernetes/apps/*/kustomization.yaml, distinct from their app dir), and none of the 9 PVCs had Velero coverage — matches the issue exactly. Fixed by adding a home-assistant-daily Schedule (PVC-scoped, 06:45 stagger slot) in kubernetes/infrastructure/post-crds/velero-schedules.yaml. Deliberately left out of velero-bootstrap-restore's SCHEDULES list since home-assistant-config already has its own bootstrap-restore path via the HA pod's seed initContainer pulling the native HAOS backup from Garage — layering an automatic Velero PVC restore on top needs separate review, same as the existing openbao-daily exclusion. PR: gitea_admin/homelab#217

Verified against origin/master (07c93e4): confirmed. home-assistant, esphome, shelly-manager, matter-server, otbr, whisper, speech-to-phrase, and zone-configurator all deploy into the home-assistant namespace (matter-server/otbr/whisper/speech-to-phrase/zone-configurator each set namespace: home-assistant in their own kubernetes/apps/*/kustomization.yaml, distinct from their app dir), and none of the 9 PVCs had Velero coverage — matches the issue exactly. Fixed by adding a home-assistant-daily Schedule (PVC-scoped, 06:45 stagger slot) in kubernetes/infrastructure/post-crds/velero-schedules.yaml. Deliberately left out of velero-bootstrap-restore's SCHEDULES list since home-assistant-config already has its own bootstrap-restore path via the HA pod's seed initContainer pulling the native HAOS backup from Garage — layering an automatic Velero PVC restore on top needs separate review, same as the existing openbao-daily exclusion. PR: https://gitea.renner.uno/gitea_admin/homelab/pulls/217
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: konairius/homelab#192