zeekayandHanzo AI
35aba18a7e
CI/CD / render (push) Failing after 0s
The host resolves and reaches this cluster, and got the ingress's own 404: bank-dash was healthy the whole time and no object named the host. PRODUCTS.md and the e2e suite both give this host to this workload. One host is enough here. dashd serves the bundle and proxies /v1 to bankd in-cluster, so the API the page calls is same-origin and answered without bankd being published. Publishing a bank's API is a separate act with a separate blast radius; it is not needed for this page to work and is not done here. Co-authored-by: Hanzo AI <[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.