Implement Google CDN for the GitLab.com Container Registry
Status update - 2022-02-01
Production rollout at 100%.
Problem to solve
To improve performance and optimize costs in the container registry, we would like to use Google Cloud CDN instead of Google Cloud Storage.
Proposal
Download requests for blobs stored in the registry will be redirected to Google Cloud CDN instead of Google Cloud Storage.
Timeline (revised 2022-01-13)
| Week | Activity | Notes |
|---|---|---|
| Jan 17 to Jan 21 | GitLab internal end-to-end Registry CDN testing in staging environment. | No user or customer impact |
| Monday, Jan 24, 2022 | Start production rollout;redirect 1% of requests to the CDN | |
| Tuesday, Jan 25, 2022 | Redirect 5% of requests to CDN | |
| Wednesday, Jan 26, 2022 | Redirect 20% of requests to CDN | |
| Thursday, Jan 27, 2022 | Redirect 60% of requests to CDN | |
| Friday, Jan 28, 2022 | Complete production rollout; redirect 100% of requests to CDN |
Questions or feedback
If you have questions or feedback, add a comment to this issue and mention @DarrenEastman .
Edited by Darren Eastman