mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-30 14:56:59 +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]>
21 lines
580 B
YAML
21 lines
580 B
YAML
apiVersion: zookeeper.pravega.io/v1beta1
|
|
kind: ZookeeperCluster
|
|
metadata:
|
|
generation: 3
|
|
labels:
|
|
cd.hanzo.ai/instance: test-cluster-zookeeper
|
|
name: test-cluster-zookeeper
|
|
namespace: zookeeper
|
|
resourceVersion: "265193"
|
|
selfLink: /apis/zookeeper.pravega.io/v1beta1/namespaces/zookeeper/zookeeperclusters/test-cluster-zookeeper
|
|
uid: eae42b94-b8ee-4fd7-9d92-30c9a30a4d5a
|
|
spec: {}
|
|
status:
|
|
externalClientEndpoint: N/A
|
|
internalClientEndpoint: 10.101.203.230:2181
|
|
members:
|
|
ready:
|
|
- test-cluster-zookeeper-0
|
|
unready: null
|
|
readyReplicas: 0
|
|
replicas: 1 |