This message was deleted.

I'm not sure how much they've published on this, but Chick-Fil-A uses a gitops workflow which involves a different repo for each store they operate - something like 2000+ repositories. They ended up building an asynchronous deployment system. Changes would be rolled out accross Git, and a custom golang agent on their deployed compute instances would do the async fetch and update. Somewhere in there, there's an API they call "Deployment Orchestrator", probably to help manage the rollout of any update, because of the async nature of it. https://medium.com/chick-fil-atech/stumbling-into-gitops-at-the-edge-92924dfb2ca1

At Bitso, we are developing a Crossplane provider for GitOps which we will release as open source soon. We're currently managing 400+ repos this way, but it can easily scale to thousands