Make GitLab Pages more resilient to GitLab downtime
Description
Sometimes during a deploy, GitLab Pages will serve 502s. It's understandable that deploying to GitLab causes downtime, but since Pages is just static assets, it really should be more resilient. Perhaps it still depends on the Postgres database to lookup DNS, for example, so it might not be trivial, but something could probably be done. One option is to leverage CloudFlare or other CDN solutions so that Pages will keep serving regardless of what happens with GitLab.
Proposal
Links / references
Documentation blurb
(Write the start of the documentation of this feature here, include:
- Why should someone use it; what's the underlying problem.
- What is the solution.
- How does someone use this
During implementation, this can then be copied and used as a starter for the documentation.)