Files
zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai
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]>
2026-07-28 16:32:14 -07:00

70 lines
2.3 KiB
YAML

apiVersion: policy.open-cluster-management.io/v1beta1
kind: OperatorPolicy
metadata:
name: install-cd
generation: 1
namespace: local-cluster
spec:
complianceConfig:
catalogSourceUnhealthy: Compliant
deploymentsUnavailable: NonCompliant
upgradesAvailable: Compliant
complianceType: musthave
remediationAction: inform
removalBehavior:
clusterServiceVersions: Delete
customResourceDefinitions: Keep
operatorGroups: DeleteIfUnused
subscriptions: Delete
severity: high
subscription:
channel: alpha
name: cd-operator
source: community-operators
sourceNamespace: openshift-marketplace
upgradeApproval: None
versions: []
status:
compliant: NonCompliant
conditions:
- lastTransitionTime: '2024-07-29T15:20:48Z'
message: CatalogSource was found
reason: CatalogSourcesFound
status: 'False'
type: CatalogSourcesUnhealthy
- lastTransitionTime: '2024-07-29T15:20:48Z'
message: >-
NonCompliant; the policy spec is valid, the policy does not specify an
OperatorGroup but one already exists in the namespace - assuming that
OperatorGroup is correct, the Subscription required by the policy was
not found, there are no relevant InstallPlans in the namespace, the
ClusterServiceVersion required by the policy was not found, no CRDs were
found for the operator, there are no relevant deployments because the
ClusterServiceVersion is missing, CatalogSource was found
reason: NonCompliant
status: 'False'
type: Compliant
- lastTransitionTime: '2024-07-29T15:20:48Z'
message: the Subscription required by the policy was not found
reason: SubscriptionMissing
status: 'False'
type: SubscriptionCompliant
relatedObjects:
- compliant: Compliant
object:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: community-operators
namespace: openshift-marketplace
reason: Resource found as expected
- compliant: NonCompliant
object:
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: cd-operator
namespace: openshift-operators
reason: Resource not found but should exist
resolvedSubscriptionLabel: cd-operator.openshift-operators