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]>
35 lines
896 B
YAML
35 lines
896 B
YAML
apiVersion: batch/v1
|
|
kind: CronJob
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/tracking-id: test-cronjob:batch/CronJob:test-cronjob/hello
|
|
labels:
|
|
app.kubernetes.io/instance: test-cronjob
|
|
name: hello
|
|
namespace: test-cronjob
|
|
spec:
|
|
jobTemplate:
|
|
spec:
|
|
template:
|
|
spec:
|
|
containers:
|
|
- command:
|
|
- /bin/sh
|
|
- '-c'
|
|
- date; echo Hello from the Kubernetes cluster
|
|
image: busybox:1.28
|
|
imagePullPolicy: IfNotPresent
|
|
name: hello
|
|
restartPolicy: OnFailure
|
|
schedule: '* * * * *'
|
|
status:
|
|
active:
|
|
- apiVersion: batch/v1
|
|
kind: Job
|
|
name: hello-29231490
|
|
namespace: test-cronjob
|
|
resourceVersion: '21226'
|
|
uid: 996e6ed6-8494-4c9a-9862-93de4af310cb
|
|
lastScheduleTime: '2025-07-30T13:46:00Z'
|
|
lastSuccessfulTime: '2025-07-30T13:44:19Z'
|