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]>
29 lines
731 B
YAML
29 lines
731 B
YAML
apiVersion: cert-manager.io/v1alpha2
|
|
kind: Issuer
|
|
metadata:
|
|
creationTimestamp: "2019-02-15T19:23:48Z"
|
|
generation: 1
|
|
name: test-issuer
|
|
namespace: cd
|
|
resourceVersion: "68352438"
|
|
selfLink: /apis/cert-manager.io/v1alpha2/namespaces/cd/issuers/test-issuer
|
|
uid: 37f408e3-3157-11e9-be3f-42010a800011
|
|
spec:
|
|
acme:
|
|
email: [email protected]
|
|
http01: {}
|
|
privateKeySecretRef:
|
|
key: ""
|
|
name: letsencrypt
|
|
server: https://acme-v02.api.letsencrypt.org/directory124
|
|
status:
|
|
acme:
|
|
uri: ""
|
|
conditions:
|
|
- lastTransitionTime: "2019-02-15T19:23:53Z"
|
|
message: |
|
|
Failed to verify ACME account: acme: : 404 page not found
|
|
reason: ErrRegisterACMEAccount
|
|
status: "False"
|
|
type: Ready
|