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]>
36 lines
911 B
YAML
36 lines
911 B
YAML
apiVersion: grafana.integreatly.org/v1beta1
|
|
kind: GrafanaDatasource
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/sync-wave: '3'
|
|
cd.hanzo.ai/tracking-id: foobar-admin:grafana.integreatly.org/GrafanaDatasource:foo/cluster-local
|
|
name: cluster-local
|
|
namespace: foo
|
|
spec:
|
|
allowCrossNamespaceImport: true
|
|
datasource:
|
|
access: proxy
|
|
editable: true
|
|
isDefault: true
|
|
jsonData:
|
|
httpHeaderName1: Authorization
|
|
timeInterval: 5s
|
|
tlsSkipVerify: true
|
|
name: cluster-local
|
|
secureJsonData:
|
|
httpHeaderValue1: Bearer ${token}
|
|
type: prometheus
|
|
url: https://thanos-querier.openshift-monitoring.svc.cluster.local:9091
|
|
instanceSelector:
|
|
matchLabels:
|
|
dashboards: grafana
|
|
resyncPeriod: 5m
|
|
valuesFrom:
|
|
- targetPath: secureJsonData.httpHeaderValue1
|
|
valueFrom:
|
|
secretKeyRef:
|
|
key: token
|
|
name: grafana-token
|
|
status:
|
|
uid: ""
|