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

resourceinclusion not working in openshift gitops 1.3

XMLWordPrintable

    • 3
    • False
    • False
    • Hide
      == Fixed issues

      Previously, the Argo CD Operator managed the `resource.exclusion` field by itself but ignored the `resource.inclusion` field. This prevented the `resource.inclusion` field configured in the `Argo CD` CR to generate in the `argocd-cm` configuration map. This bug is fixed. link:https://issues.redhat.com/browse/GITOPS-1518[GITOPS-1518]
      Show
      == Fixed issues Previously, the Argo CD Operator managed the `resource.exclusion` field by itself but ignored the `resource.inclusion` field. This prevented the `resource.inclusion` field configured in the `Argo CD` CR to generate in the `argocd-cm` configuration map. This bug is fixed. link: https://issues.redhat.com/browse/GITOPS-1518 [ GITOPS-1518 ]
    • GITOPS Sprint 210

      ArgoCD operator itself properly handles the resource.exclusion but it completely ignores the resource.inclusion.
      i tried the below scenerio:

      resourceExclusions work fine:

      1. Below lines added in argoCD CR:

      $ oc edit argocd openshift-gitops
  resourceExclusions: |
    - apiGroups:
      - tekton.dev
      clusters:
      - '*'
      kinds:
      - TaskRun

      2. resource.exclusions added in configmap automatically:

      $ oc get cm argocd-cm -o yaml
  resource.exclusions: |
    - apiGroups:
      - tekton.dev
      clusters:
      - '*'
      kinds:
      - TaskRun

      resourceInclusions does not work :

      1. Below lines added in argoCD CR:

      $ oc get argoCD -o yaml
  resourceInclusions: |
    - apiGroups:
      - tekton.dev
      clusters:
      - '*'
      kinds:
      -  DaemonSet
      • Nothing appeared on config map.
        $ oc get cm argocd-cm -o yaml

              jrao@redhat.com Jaideep Rao
              rhn-support-naygupta Nayantara Gupta (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: