Why we are not leaving the cloud

What this post added

This post details GitLab's decision to remain in the cloud after initially considering a move to bare metal. It summarizes community feedback and technical considerations regarding cost, performance, storage, networking, and distributed file systems (Ceph) that influenced the decision. The post highlights the trade-offs between cloud and bare metal infrastructure for a large-scale service like GitLab.com, emphasizing the complexity of managing on-premises infrastructure at scale and the benefits of cloud elasticity and managed services.