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
545 B
YAML
26 lines
545 B
YAML
apiVersion: cluster.x-k8s.io/v1beta1
|
|
kind: MachinePool
|
|
metadata:
|
|
labels:
|
|
cd.hanzo.ai/instance: foo
|
|
cluster.x-k8s.io/cluster-name: foo
|
|
name: foo-pool
|
|
namespace: default
|
|
spec:
|
|
clusterName: foo
|
|
replicas: 3
|
|
template:
|
|
metadata: {}
|
|
spec:
|
|
bootstrap:
|
|
dataSecretName: ""
|
|
clusterName: foo
|
|
infrastructureRef:
|
|
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
|
|
kind: AWSManagedMachinePool
|
|
name: foo-pool
|
|
namespace: default
|
|
version: v1.30.0
|
|
status:
|
|
phase: Failed
|