Codefresh

How are you structuring ArgoCD at scale?

Lately I’ve been thinking a lot about how folks structure their GitOps repositories and workflows with Argo CD once things start growing. In the beginning everything feels simple: a couple services, maybe one cluster, a staging and a prod environment. Almost any structure works. But after some time the platform grows. More services appear, more clusters, more environments, sometimes more teams. At that point the repository structure and the ApplicationSet strategy suddenly become very important