mirror of
https://github.com/hanzoai/cd.git
synced 2026-10-30 14:56:45 +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]>
49 lines
2.3 KiB
YAML
49 lines
2.3 KiB
YAML
tests:
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Waiting for the status to be reported
|
|
inputPath: testdata/progressing_no_status.yaml
|
|
- healthStatus:
|
|
status: Degraded
|
|
message: >-
|
|
NonCompliant; the policy spec is valid, the policy does not specify an
|
|
OperatorGroup but one already exists in the namespace - assuming that
|
|
OperatorGroup is correct, the Subscription required by the policy was
|
|
not found, there are no relevant InstallPlans in the namespace, the
|
|
ClusterServiceVersion required by the policy was not found, no CRDs were
|
|
found for the operator, there are no relevant deployments because the
|
|
ClusterServiceVersion is missing, CatalogSource was found
|
|
inputPath: testdata/degraded.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Waiting for the status to be updated
|
|
inputPath: testdata/progressing_old_generation.yaml
|
|
- healthStatus:
|
|
status: Progressing
|
|
message: Waiting for the compliance condition
|
|
inputPath: testdata/progressing_no_compliance.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: >-
|
|
Compliant; the policy spec is valid, the policy does not specify an
|
|
OperatorGroup but one already exists in the namespace - assuming that
|
|
OperatorGroup is correct, the Subscription matches what is required by
|
|
the policy, no InstallPlans requiring approval were found,
|
|
ClusterServiceVersion (cd-operator.v0.11.0) - install strategy
|
|
completed with no errors, there are CRDs present for the operator, all
|
|
operator Deployments have their minimum availability, CatalogSource was
|
|
found
|
|
inputPath: testdata/healthy_no_generation.yaml
|
|
- healthStatus:
|
|
status: Healthy
|
|
message: >-
|
|
Compliant; the policy spec is valid, the policy does not specify an
|
|
OperatorGroup but one already exists in the namespace - assuming that
|
|
OperatorGroup is correct, the Subscription matches what is required by
|
|
the policy, no InstallPlans requiring approval were found,
|
|
ClusterServiceVersion (cd-operator.v0.11.0) - install strategy
|
|
completed with no errors, there are CRDs present for the operator, all
|
|
operator Deployments have their minimum availability, CatalogSource was
|
|
found
|
|
inputPath: testdata/healthy_with_generation.yaml
|