zoo/universe
2
0
Fork 0
Code Issues Pull Requests Releases Activity

docs(zoo-kms): clarify repoint reversibility (operator-generated ingress)

Browse Source 
Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-07-14 10:55:43 -07:00
co-authored by Hanzo Dev
parent be899471ee
commit 5b9d46d401
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
LLM.md
+3 -1
View File
@@ -343,7 +343,9 @@ script/predict_org_safes.sh`, proven vs live Lux):
`kms.zoo.network`/`mpc.zoo.network` are hanzo-operator-managed Ingresses in
`do-sfo3-hanzo-k8s` (`hanzo-domains-*` → svc `kms:80` / hanzo-mpc). Cutover = drop from the
`hanzo-domains` CR + apply `k8s/zoo-{kms,mpc}/ingress.yaml` in the zoo cluster + move DNS to
the zoo-ingress LB. Backups: `scratchpad/ingress-backup/`. Safe (zero secrets) but HELD.
the zoo-ingress LB. REVERSIBLE: the hanzo-side Ingresses are hanzo-operator-GENERATED from
the `hanzo-domains` CR, so re-adding the CR entry restores the old routing (point-in-time
YAML also captured this session). Safe (zero secrets) but HELD for owner go.
### Lux KMS reality (step 6 answer)
`lux-kms-go/kms-0` (v1.11.8) runs **SECRETS-ONLY**: `MPC_VAULT_ID=""` + `ZAP_PORT=0` — it