mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
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]>
31 lines
960 B
YAML
31 lines
960 B
YAML
apiVersion: apps.hanzo.ai/v1alpha1
|
|
kind: AnalysisRun
|
|
metadata:
|
|
name: canary-demo-analysis-template-6c6bb7cf6f-zvcmx
|
|
namespace: default
|
|
spec:
|
|
analysisSpec:
|
|
metrics:
|
|
- failureCondition: len(result) == 0
|
|
name: memory-usage
|
|
provider:
|
|
prometheus:
|
|
address: 'http://prometheus-operator-prometheus.prometheus-operator:9090'
|
|
query: >
|
|
sum(rate(nginx_ingress_controller_requests{ingress="canary-demo-preview",status!~"[4-5].*"}[2m]))
|
|
/
|
|
sum(rate(nginx_ingress_controller_requests{ingress="canary-demo-preview"}[2m]))
|
|
successCondition: len(result) > 0
|
|
status:
|
|
metricResults:
|
|
- count: 1
|
|
measurements:
|
|
- finishedAt: '2019-10-28T18:20:37Z'
|
|
startedAt: '2019-10-28T18:20:37Z'
|
|
phase: Successful
|
|
value: '[0.965324384787472]'
|
|
name: memory-usage
|
|
phase: Successful
|
|
successful: 1
|
|
phase: Successful
|