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]>
26 lines
743 B
YAML
26 lines
743 B
YAML
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
annotations:
|
|
kubectl.kubernetes.io/last-applied-configuration: |
|
|
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"cd-metrics","namespace":"cd"},"spec":{"ports":[{"name":"http","port":8082,"protocol":"TCP","targetPort":8082}],"selector":{"app":"cd-server"}}}
|
|
creationTimestamp: 2018-10-27T06:36:27Z
|
|
name: cd-metrics
|
|
namespace: cd
|
|
resourceVersion: "1131"
|
|
selfLink: /api/v1/namespaces/cd/services/cd-metrics
|
|
uid: a1f65069-d9b2-11e8-b3c1-9ae2f452bd03
|
|
spec:
|
|
clusterIP: 10.96.199.2
|
|
ports:
|
|
- name: http
|
|
port: 8082
|
|
protocol: TCP
|
|
targetPort: 8082
|
|
selector:
|
|
app: cd-server
|
|
sessionAffinity: None
|
|
type: ClusterIP
|
|
status:
|
|
loadBalancer: {}
|