homelab

GitOps source for the Renner homelab cluster. Flux applies master to production, so every merge is a production change. Changes go in by pull request only; see CONTRIBUTING.md for YAML conventions.

Change rules that protect Home Assistant

Owner decision (REN-240, REN-243). Home Assistant runs the house, so it gets two rules on top of normal review.

1. Disruptive work runs only 02:00–05:00 Europe/Berlin

Planned work that can restart Home Assistant or disrupt the cluster is merged and applied only between 02:00 and 05:00 Europe/Berlin. That covers:

• node drain, node reboot, Talos upgrade
• CNI (Cilium, Multus) and cluster-wide network policy
• storage (Rook/Ceph, CSI, snapshot controller, CNPG operator)
• Flux core (kubernetes/clusters/*/flux-system/, Flux controllers)
• Authentik
• OpenBao, including secret rotation that restarts consumers
• anything in kubernetes/apps/home-assistant/

A PR in this list states in its description that it waits for the window. Flux applies on merge, so "wait for the window" means merge in the window, not just apply. If unsure whether a change is disruptive, treat it as disruptive.

Not covered: Home Assistant image bumps by Flux image automation. They stay fully automatic by owner decision. If one breaks Home Assistant, roll it back with RUNBOOK-home-assistant-image-rollback.md. An incident rollback is not planned work; the owner decides its timing.

2. HA-impact review before merge

Every PR that touches kubernetes/apps/home-assistant/, or makes a cluster-wide disruptive change from the list above, needs an HA-impact review before merge: a named reviewer states in the PR what Home Assistant will notice (restart, lost integration, lost history, none) and approves.

• Reviewer: Hestia, the Home Assistant maintainer.
• Until Hestia exists: the owner does the HA-impact review.

This is in addition to the normal review and merge by Argus. Argus does not merge such a PR without the HA-impact approval.