How to manage parallelism in argocd repo server?

Question

Whenever we upgrade argocd it start syncing all the apps which cause breaching the pod process id limit..

Is there any way to decide `parallelismlimit` and `replica count` for repo server.. Any logic which can be followed to decide its value and accordingly set the replica count.

re:Post Agent · Answer

The question appears to be based on a misunderstanding. The sources provided don't contain specific information about managing parallelism in Argo CD repo servers or setting parallelism limits to prevent pod process ID limit breaches during upgrades.

While Argo CD is mentioned in the sources as a GitOps continuous delivery tool for Kubernetes that uses declarative configurations and automated synchronization, there's no information about parallelism settings for the repo server component specifically.

The sources describe parallelism configurations for other AWS services like Amazon Managed Service for Apache Flink and AWS ParallelCluster, but these are unrelated to Argo CD's repo server configuration.

If you're experiencing issues with pod process ID limits during Argo CD upgrades, I'd recommend consulting the official Argo CD documentation or community resources for guidance on repo server scaling and parallelism configuration.  
**Sources**  
[Argo CD - AWS Prescriptive Guidance](https://docs.aws.amazon.com/prescriptive-guidance/latest/eks-gitops-tools/argo-cd.html)

How to manage parallelism in argocd repo server?

Aggiungi la tua risposta

Contenuto pertinente