mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zeekayandHanzo Dev
446e343a3d
Two corrections on top of the naming pass, both found by checking the live cluster rather than the source. The rename had silently changed the user-facing annotation key from argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live Applications carry the old key, so deploying that would have ignored every sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*, and universe 575650286 moves the ApplicationSet template that stamps it, so the controller regenerates all 63 consistently. The API group in code said argoproj.io/v1alpha1 in 157 places while the cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are applications.apps.hanzo.ai). Code now matches what is actually served. The legacy applications.argoproj.io/app-name label had ZERO live users, so it went with the rest. foo.argoproj.io test fixtures became foo.example.com — arbitrary test domains should not carry a vendor name. go build ./... exit 0. Co-authored-by: Hanzo Dev <[email protected]>
760 B
760 B
Disaster Recovery
You can use cd admin to import and export all Hanzo CD data.
Make sure you have ~/.kube/config pointing to your Hanzo CD cluster.
Figure out what version of Hanzo CD you're running:
cd version | grep server
# ...
export VERSION=v1.0.1
Export to a backup:
docker run -v ~/.kube:/home/cd/.kube --rm quay.io/argoproj/cd:$VERSION cd admin export > backup.yaml
Import from a backup:
docker run -i -v ~/.kube:/home/cd/.kube --rm quay.io/argoproj/cd:$VERSION cd admin import - < backup.yaml
Note
If you are running Hanzo CD on a namespace different than default remember to pass the namespace parameter (-n ). 'cd admin export' will not fail if you run it in the wrong namespace.