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]>
26 lines
810 B
YAML
26 lines
810 B
YAML
tests:
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: "0/1 node(s) are ready"
|
|
inputPath: testdata/initializing.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: "1/1 node(s) are ready"
|
|
inputPath: testdata/ready.yaml
|
|
- healthStatus:
|
|
status: Unknown
|
|
message: "Cluster is paused"
|
|
inputPath: testdata/paused.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: "Cluster is stopping (1/2 node(s) are ready)"
|
|
inputPath: testdata/stopping.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: "Cluster is on error: we lost node"
|
|
inputPath: testdata/error.yaml
|
|
- healthStatus:
|
|
status: Unknown
|
|
message: "Cluster status is unknown. Ensure your Hanzo CD is current and then check for/file a bug report: https://github.com/argoproj/argo-cd/issues"
|
|
inputPath: testdata/unknown.yaml
|