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]>
27 lines
685 B
YAML
27 lines
685 B
YAML
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
annotations:
|
|
kubernetes.io/ingress.class: nginx
|
|
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
|
|
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
|
|
creationTimestamp: 2018-09-20T06:47:27Z
|
|
generation: 9
|
|
name: cd-server-ingress
|
|
namespace: cd
|
|
resourceVersion: "23207680"
|
|
selfLink: /apis/networking.k8s.io/v1/namespaces/cd/ingresses/cd-server-ingress
|
|
uid: 09927cae-bca1-11e8-bbd2-42010a8a00bb
|
|
spec:
|
|
rules:
|
|
- host: example.apps.hanzo.ai
|
|
http:
|
|
paths:
|
|
- backend:
|
|
serviceName: cd-server
|
|
servicePort: https
|
|
status:
|
|
loadBalancer:
|
|
ingress:
|
|
- ip: 1.2.3.4
|