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

69 lines
2.2 KiB
YAML

apiVersion: apps.hanzo.ai/v1alpha1
kind: Rollout
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.hanzo.ai/v1alpha1","kind":"Rollout","metadata":{"annotations":{},"name":"example-rollout-canary","namespace":"default"},"spec":{"minReadySeconds":30,"replicas":5,"revisionHistoryLimit":3,"selector":{"matchLabels":{"app":"guestbook"}},"strategy":{"canary":{"steps":[{"setWeight":20},{"pause":{"duration":20}},{"setWeight":40},{"pause":{}}]}},"template":{"metadata":{"labels":{"app":"guestbook"}},"spec":{"containers":[{"image":"quay.io/argoprojlabs/cd-e2e-container:0.1","name":"guestbook","ports":[{"containerPort":80}]}]}}}}
rollout.apps.hanzo.ai/revision: "2"
clusterName: ""
creationTimestamp: 2019-04-26T20:17:43Z
generation: 1
name: example-rollout-canary
namespace: default
resourceVersion: "696688"
selfLink: /apis/apps.hanzo.ai/v1alpha1/namespaces/default/rollouts/example-rollout-canary
uid: 58f6f1bb-6860-11e9-b8d7-025000000001
spec:
minReadySeconds: 30
replicas: 5
revisionHistoryLimit: 3
selector:
matchLabels:
app: guestbook
strategy:
canary:
steps:
- setWeight: 20
- pause:
duration: 20
- setWeight: 40
- pause: {}
template:
metadata:
creationTimestamp: null
labels:
app: guestbook
spec:
containers:
- image: quay.io/argoprojlabs/cd-e2e-container:0.2
name: guestbook
ports:
- containerPort: 80
resources: {}
status:
HPAReplicas: 5
availableReplicas: 5
blueGreen: {}
canary:
stableRS: df986d68
conditions:
- lastTransitionTime: 2019-04-26T20:18:05Z
lastUpdateTime: 2019-04-26T20:18:05Z
message: Rollout is not serving traffic from the active service.
reason: Available
status: "False"
type: Available
- lastTransitionTime: 2019-04-26T20:18:58Z
lastUpdateTime: 2019-04-26T20:19:29Z
message: ReplicaSet "example-rollout-canary-6b566f47b7" is progressing.
reason: ReplicaSetUpdated
status: "True"
type: Progressing
currentPodHash: 6b566f47b7
currentStepHash: 6567fc959c
currentStepIndex: 3
observedGeneration: 6df79499bc
readyReplicas: 5
replicas: 5
selector: app=guestbook
updatedReplicas: 2