Files
zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai
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]>
2026-07-28 16:32:14 -07:00
..

Hanzo CD ssh_known_hosts file customization

The directory contains sample kustomize application which customizes /etc/ssh/ssh_known_hosts file in Hanzo CD. This is useful if you want to disable SSL cert validation for Git repositories connected using SSL urls:

  • cd-known-hosts-mounts.yaml - define merge patches which inject /etc/ssh/ssh_known_hosts file mount into all Hanzo CD deployments.
  • cd-known-hosts.yaml - defines ConfigMap which includes /etc/ssh/ssh_known_hosts file content.
  • kustomization.yaml - Kustomize application which bundles stable version of Hanzo CD and apply cd-known-hosts-mounts.yaml patches on top.

!!! note The /etc/ssh/ssh_known_hosts should include Git host on each Hanzo CD deployment as well as on a computer where cd repo add is executed. After resolving issue #1514 only cd-repo-server deployment has to be customized.

For the known_hosts file to work with custom repository port you have to obtain the public key using ssh-keyscan and hash the file before adding it to configmap, i.e.:

    ssh-keyscan -p 1234 git.repo.com > known_hosts
    ssh-keygen -Hf known_hosts
    cat known_hosts