Why GitLab.com is changing its CDN provider to Cloudflare March 28

What this post added

This post announces the migration of GitLab.com's CDN from Fastly to Cloudflare. The primary technical drivers for this migration are to improve availability, security, and performance by leveraging Cloudflare's Web Application Firewall (WAF), Spectrum (for port 22 traffic), and Argo Smart Routing. The migration is complex because GitLab.com serves both HTTPS and SSH (port 22) traffic, requiring a CDN solution capable of handling both. The post details the timing of the switch (March 28, 2020), the need for users with firewalled access to update their IP whitelists to Cloudflare's ranges, and potential impacts on custom/private runners due to DNS or SSL certificate caching. It also mentions the use of a readiness review to plan the transition.