mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zeekayandHanzo Dev
446e343a3d
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]>
40 lines
720 B
YAML
40 lines
720 B
YAML
redis-ha:
|
|
auth: true
|
|
authKey: auth
|
|
existingSecret: cd-redis
|
|
persistentVolume:
|
|
enabled: false
|
|
redis:
|
|
masterGroupName: cd
|
|
config:
|
|
save: '""'
|
|
bind: '0.0.0.0'
|
|
haproxy:
|
|
enabled: true
|
|
IPv6:
|
|
enabled: false
|
|
image:
|
|
tag: 3.0.8-alpine
|
|
timeout:
|
|
server: 6m
|
|
client: 6m
|
|
checkInterval: 3s
|
|
metrics:
|
|
enabled: true
|
|
extraConfig: |
|
|
global
|
|
maxconn 4096
|
|
serviceAccount:
|
|
automountToken: true
|
|
image:
|
|
tag: 8.6.4-alpine
|
|
sentinel:
|
|
bind: '0.0.0.0'
|
|
lifecycle:
|
|
postStart:
|
|
exec:
|
|
command:
|
|
- '/bin/sh'
|
|
- '-c'
|
|
- 'sleep 30; redis-cli -p 26379 sentinel reset cd'
|