hanzo-dev
e530eeec7c
A universe is values files, so what breaks is a file the chart can no longer template -- and today that is invisible until CD syncs and the service is already down. Rendering every file against the chart CD will use, at the version CD will use, moves that failure onto the push that caused it. CI does not deploy: applying is CD's one job, and a second path means the cluster can disagree with git while both report success. Two files moved out of deploy/ because they are not values at all -- the generator globs deploy/*/*.yaml, so a tunnel config sitting there becomes an Application that cannot render.
Lux Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/lux/universe
This tip is an ancestor of canonical main, so no commit reachable from this
branch is unique to it — the canonical repo is a strict superset. Nothing was
lost by stopping here.
Two universes for one org is a split brain: a push lands somewhere real, reports
success, and never reaches a cluster, because CD reconciles the other one
(deploy/applicationset.yaml names the canonical URL). One repo per org means
that failure cannot happen.