Files
zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai
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]>
2026-07-28 16:32:14 -07:00

92 lines
2.4 KiB
YAML

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
creationTimestamp: '2021-06-24T11:30:12Z'
finalizers:
- trident.netapp.io
generation: 1
labels:
app.kubernetes.io/instance: trident-config
managedFields:
- apiVersion: trident.netapp.io/v1
fieldsType: FieldsV1
fieldsV1:
'f:metadata':
'f:annotations':
.: {}
'f:kubectl.kubernetes.io/last-applied-configuration': {}
'f:labels':
.: {}
'f:app.kubernetes.io/instance': {}
'f:spec':
.: {}
'f:backendName': {}
'f:credentials':
.: {}
'f:name': {}
'f:dataLIF': {}
'f:defaults':
.: {}
'f:exportPolicy': {}
'f:snapshotPolicy': {}
'f:snapshotReserve': {}
'f:spaceReserve': {}
'f:deletionPolicy': {}
'f:limitVolumeSize': {}
'f:managementLIF': {}
'f:nfsMountOptions': {}
'f:storageDriverName': {}
'f:storagePrefix': {}
'f:svm': {}
'f:version': {}
manager: cd-application-controller
operation: Update
time: '2021-06-24T11:30:12Z'
- apiVersion: trident.netapp.io/v1
fieldsType: FieldsV1
fieldsV1:
'f:metadata':
'f:finalizers':
.: {}
'v:"trident.netapp.io"': {}
'f:status':
.: {}
'f:backendInfo':
.: {}
'f:backendName': {}
'f:backendUUID': {}
'f:deletionPolicy': {}
'f:lastOperationStatus': {}
'f:message': {}
'f:phase': {}
manager: trident_orchestrator
operation: Update
time: '2021-06-24T11:30:12Z'
name: backend-tbc-ontap-nas
namespace: trident
resourceVersion: '3429076'
uid: 3de31983-aff9-4adb-a31c-1541d2cd86e6
spec:
backendName: tbc-ontap-nas
credentials:
name: backend-ontap-nas-secret
dataLIF: 1.1.1.1
defaults:
exportPolicy: ep_000
snapshotPolicy: default
snapshotReserve: '10'
spaceReserve: volume
deletionPolicy: retain
limitVolumeSize: 100Gi
managementLIF: 1.1.1.1
nfsMountOptions: nfsvers=4
storageDriverName: ontap-nas
storagePrefix: trident-play01
svm: svm-trident-play
version: 1
status:
deletionPolicy: retain
lastOperationStatus: Progressing
message: Creating 'tbc-ontap-nas' backend
phase: Bound