[Deprecated / to be replaced] Enable dual deployment to Cloudflare DNS
C4
Production Change - Criticality 4Change Objective | Enable dual deployment to Cloudflare DNS |
---|---|
Change Type | ConfigurationChange |
Services Impacted |
about-src. , altssh. , canary. , registry.gke. , registry. , shared-runners-manager-*. on staging.gitlab.com. SSH and HTTPS for staging.gitlab.com are not affected |
Change Team Members | @T4cC0re |
Change Severity | C4 |
Change Reviewer or tested in staging | This change only affects staging. Terraform output was reviewed within the linked MR. |
Dry-run output | If the change is done through a script, it is mandatory to have a dry-run capability in the script, run the change in dry-run mode and output the result |
Due Date | TBD |
Time tracking | <1 hour |
Detailed steps for the change
note ~"workflow::Blocked" by https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8697 via https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/merge_requests/1255.
- Get a backup of the Zonefile of staging.gitlab.com. via the Cloudflare Web UI
- Manually remove DNS entries from staging.gitlab.com. via the Cloudflare Web UI
- Merge https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/merge_requests/1255 and apply the
dns
pipeline - The records should re-appear within Cloudflare. If they do not, perform a rollback.
Rollback steps
- Revert https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/merge_requests/1255
- Restore the zonefile backup via the Cloudflare Web UI
Changes checklist
-
Detailed steps and rollback steps have been filled prior to commencing work -
Person on-call has been informed prior to change being rolled out
Edited by Hendrik Meyer (xLabber)