Form Initiator: madgupta@redhat.com

Customer Name: Clearstream Services

Business Impact:

As per sales:

"Clearstream is investing a lot into Red Hat with multiple consulting deals worth 400K$+ and expanding OpenShift growth.

The slow convergence of ArgoCD is impacting their development teams, so there is a production impact.

They have paid Red hat before to investigate this with consulting, with no concrete outcomes. It seems we have now reached a critical point with their GitOps instance.

I'm escalating because I don't see any progress on support/engineering: https://issues.redhat.com/browse/GITOPS-6364

We need a high focus on this issue"

Escalation Ticket: https://access.redhat.com/watchlist/internal/watchlist/82382

Description:

We have two ArgoCD instances running in our cluster - the default openshift-gitops instance created by the operator and a custom argocd instance. When syncing applications through the default instance, the process completes as expected. However, when syncing through our custom argocd instance, we observe significantly longer processing times.

The controller logs reveal that the sync process gets stuck after the GetRepoObjs stats phase, specifically after the message:

"GetRepoObjs stats" application=argocd/gitops-test-app2 build_options_ms=0 helm_ms=0 plugins_ms=0 repo_ms=0 time_ms=159 unmarshal_ms=159 version_ms=0