有人在多个集群中扩展 ArgoCD 吗？
我一直在使用 ArgoCD 和 GitHub Actions 进行 GitOps，最开始效果很好。但一旦我开始管理多个集群，情况变得更加复杂：
- 同步速度变慢
- 需要启动独立的 ArgoCD 实例
- CI/CD 感觉与 GitOps 流程脱节
我想听听其他人在大规模实施 GitOps 时的做法。你们是继续使用 Argo 并增加工具层，还是转向 Flux 或自定义设置？任何经验教训都欢迎分享。
查看原文
I’ve been using ArgoCD with GitHub Actions for GitOps, and it worked well in the beginning. But once I started managing multiple clusters, it got more complicated:<p>- Syncs slowed down<p>- Had to spin up separate ArgoCD instances<p>- CI/CD felt disconnected from the GitOps flow<p>Would like to hear how others have approached GitOps at scale. Did you stick with Argo and layer on tooling? Or move to something like Flux or a custom setup? Any lessons learned are welcome.