Blog Post about moving GitLab.com to Cloudflare for CDN, WAF, DDOS protection January 16, 2020

Proposal

Over the summer of 2019, the infrastructure and sec-ops teams did an evaluation of vendors to pick a vendor our future needs for Content Delivery Network (CDN), Web Application Firewall, and DDOS protection. In that time, we picked Cloudflare as our vendor. As we now have come closer to doing a switchover, we have realized, we need to broadcast our plans for this switch before we implement it for GitLab.com and about.gitlab.com.

cc @rebecca, @nwoods1, @marin, @glopezfernandez

adding sensitive - even though this should be invisible to users at the UI level, since this affects all GitLab.com users, we want to make sure we share this correctly.

Set issue due date to 2019-12-02, but we do not yet have a specific publish date in mind. I wanted to get this issue and blog proposal written up first.

--Changed to 2020-01-16

Checklist

• If you have a specific publish date in mind
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
• If time sensitive
  • Added ~"priority" label
  • Mentioned @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• Indicate if supporting an event or campaign