Morgan Stanley Scales Flux GitOps Across 500 Clusters Managing 100,000+ Containers
Key Takeaways
- ▸Morgan Stanley operates Flux across 500+ clusters with 100,000+ containers, demonstrating Flux's viability at enterprise scale in highly regulated industries
- ▸Implementing GitOps required addressing foundational challenges including configuration drift, cluster recovery, and the need for continuous state reconciliation rather than push-based deployments
- ▸Self-service platforms built on top of Flux, combined with strict RBAC and multi-tenancy controls, enable secure developer adoption while maintaining security and compliance requirements
Summary
Morgan Stanley has successfully deployed Flux, an open-source GitOps toolkit, across over 500 Kubernetes clusters managing more than 2,000 nodes and 100,000+ containers in production. The financial services company shared its five-year journey from traditional push-based CI/CD pipelines to a self-service GitOps platform at FluxCon NA, demonstrating how to implement continuous reconciliation, multi-tenant security controls, and performance optimization at enterprise scale. The implementation leveraged Flux's core principles of being lean, performant, extensible, and secure to address critical challenges like configuration drift and fragile recovery procedures that plagued their earlier infrastructure-as-code approach.
Morgan Stanley's deployment strategy included building a self-service onboarding platform that automated entitlement checks, change control processes, and namespace priming, allowing developers to adopt GitOps without managing low-level Kubernetes details. The company also implemented strict multi-tenancy using Kubernetes RBAC and service account impersonation to meet regulatory requirements in the highly regulated financial sector. To handle the operational complexity at scale, Morgan Stanley tuned Flux's reconciliation intervals, controller concurrency settings, and resource limits to optimize performance across tens of thousands of Flux resources without overwhelming their Kubernetes control plane.
- Performance tuning through reconciliation intervals, controller concurrency adjustment, and resource management is critical for operating GitOps infrastructure at massive scale
Editorial Opinion
Morgan Stanley's case study validates Flux's positioning as a production-ready GitOps solution capable of managing complexity at financial services scale. The company's five-year journey highlights that successful GitOps adoption requires not just tooling but cultural shifts toward continuous reconciliation and self-service patterns—a blueprint other enterprises are likely watching closely as they evaluate their own infrastructure modernization strategies.
