zeekayandHanzo Dev 1fc97343c1 Retire the workloads already scaled to zero
Each of these declares replicas: 0 -- no pod, no endpoint, no caller, and no
record of when it was parked. A declaration that runs nothing is not a
deployment, it is a note nobody can date, and it keeps a slot in every fleet
listing and every sync. Git history holds them if one was paused rather than
retired.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 20:49:39 -07:00
2026-09-08 15:28:19 -07:00
2026-09-08 15:28:19 -07:00
2026-09-03 11:04:58 -07:00
2026-09-08 15:28:19 -07:00
2026-09-08 15:28:19 -07:00
2026-02-14 05:27:03 -08:00
2026-09-08 15:28:19 -07:00
2026-03-26 22:45:36 -07:00

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.

S
Description
Declared state for the zoo fleet: one values file per service, one ApplicationSet
Readme
1.2 MiB
Languages
TypeScript 70.1%
Shell 21.5%
Makefile 8.4%