mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-30 14:56:59 +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]>
29 lines
676 B
YAML
29 lines
676 B
YAML
apiVersion: astra.netapp.io/v1
|
|
kind: Schedule
|
|
metadata:
|
|
creationTimestamp: "2024-04-15T20:46:16Z"
|
|
generation: 2
|
|
labels:
|
|
cd.hanzo.ai/instance: ghost-demo
|
|
name: ghost-monthly
|
|
namespace: astra-connector
|
|
ownerReferences:
|
|
- apiVersion: astra.netapp.io/v1
|
|
kind: Application
|
|
name: ghost
|
|
uid: 0af10ee8-772b-4367-8334-44f9e4ad2849
|
|
resourceVersion: "3231157"
|
|
uid: f75ebc6f-627c-4b34-ba36-e64ddc3948e3
|
|
spec:
|
|
appVaultRef: astra-gcp-backup-743cfd150129
|
|
applicationRef: ghost
|
|
backupRetention: "1"
|
|
dayOfMonth: "1"
|
|
dayOfWeek: ""
|
|
enabled: true
|
|
granularity: monthly
|
|
hour: "2"
|
|
minute: "0"
|
|
recurrenceRule: ""
|
|
snapshotRetention: "1"
|