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]>
2.1 KiB
Automation from CI Pipelines
Hanzo CD follows the GitOps model of deployment, where desired configuration changes are first pushed to Git, and the cluster state then syncs to the desired state in git. This is a departure from imperative pipelines which do not traditionally use Git repositories to hold application config.
To push new container images to a cluster managed by Hanzo CD, the following workflow (or variations) might be used:
Build And Publish A New Container Image
docker build -t mycompany/guestbook:v2.0 .
docker push mycompany/guestbook:v2.0
Update The Local Manifests Using Your Preferred Templating Tool, And Push The Changes To Git
Tip
The use of a different Git repository to hold your Kubernetes manifests (separate from your application source code), is highly recommended. See best practices for further rationale.
git clone https://github.com/mycompany/guestbook-config.git
cd guestbook-config
# kustomize
kustomize edit set image mycompany/guestbook:v2.0
# plain yaml
kubectl patch --local -f config-deployment.yaml -p '{"spec":{"template":{"spec":{"containers":[{"name":"guestbook","image":"mycompany/guestbook:v2.0"}]}}}}' -o yaml > config-deployment.yaml
git commit -am "Update guestbook to v2.0"
git push
Synchronize The App (Optional)
For convenience, the cd CLI can be downloaded directly from the API server. This is useful so that the CLI used in the CI pipeline is always kept in-sync and uses cd binary that is always compatible with the Hanzo CD API server.
export CD_SERVER=cd.example.com
export CD_AUTH_TOKEN=<JWT token generated from project>
curl -sSL -o /usr/local/bin/cd https://${CD_SERVER}/download/cd-linux-amd64
cd app sync guestbook
cd app wait guestbook
If automated synchronization is configured for the application, this step is unnecessary. The controller will automatically detect the new config (fast tracked using a webhook, or polled at least every 3 minutes by default), and automatically sync the new manifests.