zeekayandHanzo Dev
fe67b84914
CI/CD / render (push) Failing after 0s
Every image in zoo-mainnet except consul and the ingress is published for linux/amd64 alone, and none of these files said so. Unpinned, the scheduler is free to place them on spark, where the kubelet refuses the pull with `no match for platform in manifest` -- which reads as a broken image and is a misplaced pod. zoo-ui, zoo-gym, zoo-bot and zoo-build had been sitting in ImagePullBackOff there. The pin follows the artifact: an image that exists for one architecture may only be scheduled where that architecture is. consul and the ingress are multi-arch and stay free to land anywhere. Co-authored-by: Hanzo Dev <[email protected]>
Zoo Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/zoo/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.