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

Changing log level or log format for repo server doesn't trigger reconciliation

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      * Previously, if you changed the log level for the `argocd-repo-server` workload, the Operator didn't reconcile this setting. The workaround was to delete the deployment resource so that the Operator recreated it with the new log level. With this update, the log level is correctly reconciled for existing `argocd-repo-server` workloads. link:https://issues.redhat.com/browse/GITOPS-1387[GITOPS-1387]
      Show
      * Previously, if you changed the log level for the `argocd-repo-server` workload, the Operator didn't reconcile this setting. The workaround was to delete the deployment resource so that the Operator recreated it with the new log level. With this update, the log level is correctly reconciled for existing `argocd-repo-server` workloads. link: https://issues.redhat.com/browse/GITOPS-1387 [ GITOPS-1387 ]
    • 5
    • GITOPS Sprint 208

    Description

      Changes to .spec.repo.logLevel and .spec.repo.logFormat do not trigger reconciliation on existing argocd-repo-server deployments. Changes will only be reconciled if the deployment did not exist before, or is deleted after making the change to ArgoCD Operand.

      For details, see upstream issue: https://github.com/argoproj-labs/argocd-operator/issues/448

      Attachments

        Activity

          People

            rescott1 Regina Scott
            jfischer@redhat.com Jann Fischer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: