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

59 lines
1.5 KiB
YAML

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
annotations:
finalizers:
- finalizer.keda.sh
labels:
cd.hanzo.ai/instance: keda-default
name: keda-with-fallback
namespace: keda
resourceVersion: '160591443'
uid: 83ee438a-f383-43f3-9346-b901d9773f5c
spec:
maxReplicaCount: 10
minReplicaCount: 1
fallback:
failureThreshold: 3
replicas: 5
scaleTargetRef:
name: keda-service
triggers:
- type: prometheus
metadata:
serverAddress: http://prometheus-server.monitoring.svc.cluster.local
metricName: http_requests_total
threshold: '100'
query: sum(rate(http_requests_total{app="keda-service"}[2m]))
status:
conditions:
- message: ScaledObject is defined correctly and is ready for scaling
reason: ScaledObjectReady
status: 'True'
type: Ready
- message: Scaling is performed because triggers are active
reason: ScalerActive
status: 'True'
type: Active
- message: At least one trigger is falling back on this scaled object
reason: FallbackExists
status: 'True'
type: Fallback
- status: 'False'
type: Paused
externalMetricNames:
- s0-prometheus
health:
"prometheus":
numberOfFailures: 4
status: Failing
hpaName: keda-with-fallback-hpa
lastActiveTime: '2023-12-19T10:35:22Z'
originalReplicaCount: 1
scaleTargetGVKR:
group: apps
kind: Deployment
resource: deployments
version: v1
scaleTargetKind: apps/v1.Deployment