[jakejarvis]

via https://gitlab.com/gitlab-com/gl-infra/readiness/tree/master...:

> 1. Once traffic is ensured to flow though Cloudflare, we initiate decommission of Route53.

> We would disable the transfer lock and generate an auth code.

> immediately after, we move the domain over to the Cloudflare registry

I love the overall plan but this part would worry me... The most obvious contingency plan when you're putting so many eggs into one basket is to keep a kill-switch somewhere like your domain registrar, where you can abandon ship entirely by switching nameservers in the worst of scenarios, right?

Correct me if I'm wrong but when the Cloudflare dashboard went down a few weeks (months?) ago, no sort of DNS-level changes would have been possible. (Either way, I don't think you can even set external nameservers for domains on Cloudflare Registrar yet?)

Just curious about the thinking behind this particular move and why the pros outweigh the cons of leaving the domain where it is.