mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
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]>
1.3 KiB
1.3 KiB
Compare Options
Ignoring Resources That Are Extraneous
You may wish to exclude resources from the app's overall sync status under certain circumstances, e.g. if they are generated by a tool. This can be done by adding this annotation on the resource you wish to exclude:
metadata:
annotations:
cd.hanzo.ai/compare-options: IgnoreExtraneous
Note
This only affects the sync status. If the resource's health is degraded, then the app will also be degraded.
Kustomize has a feature that allows you to generate config maps (read more ⧉). You can set generatorOptions to add this annotation so that your app remains in sync:
configMapGenerator:
- name: my-map
literals:
- foo=bar
generatorOptions:
annotations:
cd.hanzo.ai/compare-options: IgnoreExtraneous
kind: Kustomization
Note
generatorOptionsadds annotations to both config maps and secrets (read more ⧉).
You may wish to combine this with the Prune=false sync option.
