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]>
27 lines
617 B
YAML
27 lines
617 B
YAML
apiVersion: kiali.io/v1alpha1
|
|
kind: Kiali
|
|
metadata:
|
|
finalizers:
|
|
- finalizer.kiali
|
|
generation: 1
|
|
labels:
|
|
cd.hanzo.ai/instance: kiali-default
|
|
name: kiali
|
|
namespace: kiali
|
|
resourceVersion: "344752"
|
|
selfLink: /apis/kiali.io/v1alpha1/namespaces/2269-kiali/kialis/kiali
|
|
uid: a59d8dac-900b-4e05-9cb7-cf96a0bf4b6b
|
|
spec: {}
|
|
status:
|
|
conditions:
|
|
- ansibleResult:
|
|
changed: 1
|
|
completion: 2020-06-08T13:41:20.133525
|
|
failures: 0
|
|
ok: 56
|
|
skipped: 82
|
|
lastTransitionTime: "2020-06-04T17:47:31Z"
|
|
message: Reconciling
|
|
reason: Running
|
|
status: "True"
|
|
type: Running |