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]>
36 lines
801 B
YAML
36 lines
801 B
YAML
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
annotations:
|
|
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "600"
|
|
creationTimestamp: 2018-06-05T23:34:58Z
|
|
labels:
|
|
app.kubernetes.io/instance: cd-cdp
|
|
name: cd-server
|
|
namespace: cd
|
|
resourceVersion: "32559487"
|
|
selfLink: /api/v1/namespaces/cd/services/cd-server
|
|
uid: 0f5885a9-6919-11e8-ad29-020124679688
|
|
spec:
|
|
clusterIP: 100.69.46.185
|
|
externalTrafficPolicy: Cluster
|
|
ports:
|
|
- name: http
|
|
nodePort: 30354
|
|
port: 80
|
|
protocol: TCP
|
|
targetPort: 8080
|
|
- name: https
|
|
nodePort: 31866
|
|
port: 443
|
|
protocol: TCP
|
|
targetPort: 8080
|
|
selector:
|
|
app: cd-server
|
|
sessionAffinity: None
|
|
type: LoadBalancer
|
|
status:
|
|
loadBalancer:
|
|
ingress:
|
|
- hostname: abc123.us-west-2.elb.amazonaws.com
|