Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-6701

argocd-resource-tracker should also handle resources that do not have an ownerRef, similar to how Argo CD handles such resources.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Operator
    • None
    • 5
    • GitOps Crimson Sprint 13, GitOps Crimson Sprint 14

      Story (Required)

      argocd-resource-tracker relies on ownerRef to establish parent-child relationships between resources. However, in cases where a resource does not have an ownerRef, it is not properly tracked or included in the resource relationship mapping. This behavior differs from Argo CD, which is capable of handling resources without ownerRef

      For example, Argo CD considers:

      • ClusterServiceVersion (CSV) related to OperatorGroup via annotations.
      • Secrets related to ServiceAccounts if they are service account tokens.

       

       

      Acceptance Criteria:

        • Resources without ownerRef should be properly managed, as Argo CD handles such cases.

       Resources

              rh-ee-mmeetei Mangaal Meetei
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: