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

Application-scoped Argo instance fails to sync when a managed namespace is deleted

    XMLWordPrintable

Details

    • 5
    • GITOPS Sprint 210
    • Hide
      == Fixed issues

      * When using an `Namespace-scoped` Argo CD instance, for example, an Argo CD instance that is not scoped to *All Namepsaces* in a cluster, {gitops-title} dynamically maintains a list of managed namespaces. These namespaces include the `argocd.argoproj.io/managed-by` label. This list of namespaces is stored in a cache in *Argo CD -> Settings -> Clusters -> "in-cluster" -> NAMESPACES*. Before this update, if you deleted one of these namespaces, the Operator ignored that, and the namespace remained in the list. This behavior broke the *CONNECTION STATE* in that cluster configuration, and all sync attempts resulted in errors. For example:
      +
      [source,text]
      ----
      Argo service account does not have <random_verb> on <random_resource_type> in namespace <the_namespace_you_deleted>.
      ----
      +
      This bug is fixed. link:https://issues.redhat.com/browse/GITOPS-1521[GITOPS-1521]
      Show
      == Fixed issues * When using an `Namespace-scoped` Argo CD instance, for example, an Argo CD instance that is not scoped to *All Namepsaces* in a cluster, {gitops-title} dynamically maintains a list of managed namespaces. These namespaces include the `argocd.argoproj.io/managed-by` label. This list of namespaces is stored in a cache in *Argo CD -> Settings -> Clusters -> "in-cluster" -> NAMESPACES*. Before this update, if you deleted one of these namespaces, the Operator ignored that, and the namespace remained in the list. This behavior broke the *CONNECTION STATE* in that cluster configuration, and all sync attempts resulted in errors. For example: + [source,text] ---- Argo service account does not have <random_verb> on <random_resource_type> in namespace <the_namespace_you_deleted>. ---- + This bug is fixed. link: https://issues.redhat.com/browse/GITOPS-1521 [ GITOPS-1521 ]
    • False

    Description

      When using an "Application-scoped" argocd (e.g. one that is not scoped to All Namepsaces in a cluster), the GitOps operator dynamically maintains a list of "managed namespaces", which are namespaces that include the argocd.argoproj.io/managed-by label. This list of namespaces gets cached in argocd (Settings > Clusters > "in-cluster" > NAMESPACES). However, if one of these namespaces gets deleted, the operator doesn't seem to notice, and the namespace remains in that list. This breaks both the "CONNECTION STATE" in that cluster config, and also all Sync attempts after the namespace gets deleted. The sync will show errors like <argo service account> does not have <random verb> on <random resource type> in namespace "the-namespace-you-deleted".

      https://github.com/redhat-developer/gitops-operator/issues/229{{}}

      Attachments

        Activity

          People

            jrao@redhat.com Jaideep Rao
            ncurry@redhat.com Nicholas Curry
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: