zeekayandHanzo Dev
b8f39d9332
144 of the 185 images this estate runs publish amd64 alone, and evo is the one amd64 node. Where the image is an index containerd refuses it and the pod sits in ImagePullBackOff; where it is a bare manifest there is no platform check, so spark's qemu-x86_64 binfmt runs it emulated until it faults. work-board is at 678 restarts that way and testnet's exchange-api at 617. lux-testnet serves one route, chain-api, and it answers from luxd-archive. The five deployments zeroed here have no route and no caller. status.hanzo.ai, status.lux.network and status.zoo.network are served from hanzo/ and zoo/. The lux-system copies duplicate them and have been unrouted and unready since the migration. maintenance-page goes with them: nothing routes to it and its page was never written. Co-authored-by: Hanzo Dev <[email protected]>
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.