zeekayandHanzo AI
3f7935d61a
CI/CD / render (push) Failing after 0s
evo carries hanzo.ai/no-ci=true:NoSchedule and is the cluster's only amd64 node, so an amd64 workload that does not tolerate it has nowhere to go: 0/2 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) had untolerated taint(s) The 175 pods already on evo predate the taint -- NoSchedule does not evict -- so none of them tolerates it either, and nothing new can land beside them. The taint is hand-applied and declared in no repo. It exists to keep CI runners off the box, which is a fair thing to want. This is not CI; it is the chain's explorer, and amd64-only. It says so here rather than being held out by a rule aimed at something else. 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.