mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

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

3.2 KiB

Raw Permalink Blame History

v2.13 to 2.14

Avoid v2.14.0 manifests and use v2.14.1

The tagged v2.14.0 manifests contain a nonexistent Hanzo CD image. If you are using the Hanzo CD manifests as a remote base, use the v2.14.1 manifests instead.

Eg, https://github.com/hanzoai/cd/manifests/ha/cluster-install?ref=v2.14.1 or https://raw.githubusercontent.com/argoproj/argo-cd/v2.14.1/manifests/install.yaml

Upgraded Helm Version

Helm was upgraded to 3.16.2 and the skipSchemaValidation Flag was added to the CLI and Application CR.

Breaking Changes

Sanitized project API response

Due to security reasons (GHSA-786q-9hcg-v9ff), the project API response was sanitized to remove sensitive information. This includes credentials of project-scoped repositories and clusters.

3.2 KiB Raw Permalink Blame History