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

37 lines
1000 B
YAML

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
creationTimestamp: '2022-05-13T12:39:31Z'
name: sample
uid: 0e6d855e-83ed-4ed5-b80a-461a750f14db
spec:
maxReplicas: 2
minReplicas: 1
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: cd-server
targetCPUUtilizationPercentage: 80
status:
conditions:
- lastTransitionTime: '2022-05-13T12:40:33Z'
message: >-
the HPA was able to successfully calculate a replica count from cpu
resource utilization (percentage of request)
reason: ValidMetricFound
status: 'True'
type: ScalingActive
- lastTransitionTime: '2022-05-13T12:40:31Z'
message: the desired count is within the acceptable range
reason: DesiredWithinRange
status: 'False'
type: ScalingLimited
currentMetrics:
- resource:
current:
averageUtilization: 6
averageValue: 12m
name: cpu
type: Resource
currentReplicas: 1
desiredReplicas: 1