Description
Hello team,
Gitops repo-server-timeout-seconds can not be set via the operator for the default instance.
In order to handle our workload, have scaled the repo server replicas and performed several tuning at the ArgoCD instance. However, Still, observe "Context Deadline Exceed" errors.
Based on argocd documentation, the following "--repo-server-timeout-seconds" parameters seem to cover the need, yet this parameter can not be set via an official operator.
https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/
"The manifest generation typically takes the most time during reconciliation. The duration of manifest generation is limited to make sure the controller refresh queue does not overflow. The app reconciliation fails with Context deadline exceeded error if manifest generating taking too much time. As a workaround increase the value of --repo-server-timeout-seconds and consider scaling up argocd-repo-server deployment."
Can we add this feature?
Attachments
Issue Links
- clones
-
GITOPS-2109 Support for Gitops repo-server-timeout-seconds
- Closed