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]>
25 lines
703 B
YAML
25 lines
703 B
YAML
apiVersion: operator.knative.dev/v1alpha1
|
|
kind: KnativeEventing
|
|
metadata:
|
|
finalizers:
|
|
- delete-knative-eventing-manifest
|
|
generation: 3
|
|
labels:
|
|
app: knative-eventing
|
|
cd.hanzo.ai/instance: knative-eventing
|
|
version: 0.14.1
|
|
name: knative-eventing
|
|
namespace: knative-eventing
|
|
resourceVersion: "31707154"
|
|
selfLink: /apis/operator.knative.dev/v1alpha1/namespaces/knative-eventing/knativeeventings/knative-eventing
|
|
uid: bbcb2872-4304-4541-9811-7ce5125ceadf
|
|
spec: {}
|
|
status:
|
|
conditions:
|
|
- lastTransitionTime: "2020-04-29T04:52:05Z"
|
|
status: "True"
|
|
type: InstallSucceeded
|
|
- lastTransitionTime: "2020-06-08T10:53:44Z"
|
|
status: "False"
|
|
type: Ready
|
|
version: 0.14.1 |