zeekayandHanzo Dev 0a29a27224 Take ownership of the zoo.cloud zone
The zone lived only under lux/universe/k8s/dns, where the sync script
globs every *.yaml and so held write authority over a zone belonging to
another brand. cf-zones/sync.sh globs this directory the same way, so
moving the file is the whole change -- zoo.cloud now syncs from the
universe whose brand it is.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-03 21:28:37 -07:00
2026-07-26 10:16:32 -07:00
2026-08-03 21:02:21 -07:00
2026-09-03 21:28:37 -07:00
2026-09-03 11:04:58 -07:00
2026-08-03 21:02:21 -07:00
2026-02-14 05:27:03 -08:00
2026-08-03 21:02:21 -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%