Home-Network/home-network-k3s-impl

0 Fork 0

Files

T

History

jakman85 bbd4f682a6

gate / gate (pull_request) Successful in 1m35s

Details

gate / conformance (pull_request) Has been skipped

Details

chore(plex): fresh plex.tv claim token

Injected inside the plex.tv claim window per runbooks/plex-claim.md.

2026-09-29 01:31:24 -05:00

vms

Rolled unifi console password

2026-09-19 02:49:16 +00:00

wave-0

chore(plex): fresh plex.tv claim token

2026-09-29 01:31:24 -05:00

wave-1

Added gitea action runner secret

2026-09-29 00:50:02 -05:00

wave-2

fix(obs): twelve app SLI rules read a signal that exists; kill the dead ServiceMonitors

2026-09-13 17:11:30 -05:00

README.md

refactor(apps): split monolithic apps Kustomization into dependency waves

2026-08-26 12:19:00 -05:00

README.md

apps

App-tier manifests, rendered from catalog/*.yaml ServiceDefinitions by catalog/render.py and split into dependency-ordered waves (wave-<N>/).

Each wave-<N>/ is reconciled by its own Flux Kustomization apps-wave-<N> (clusters/base/apps-wave-<N>.yaml), which dependsOn wave N-1 (wave 0 dependsOn platform-config) and health-gates (wait: true) ONLY that wave. A crashlooping workload in a later wave can no longer stall an earlier wave or block new revisions.
wave-<N>/kustomization.yaml and clusters/base/apps-wave-<N>.yaml are generated — run python3 catalog/render.py --emit-waves after onboarding a service; do not hand-edit them.
Wave assignment = longest dependency-path depth over the catalog dependencies: graph; a co-located CNPG database <svc>-db is a leaf and always lands strictly below its consumer.

See ../DESIGN-waves.md for the wave table, Flux topology, and the cutover runbook.