Corrective Action: The CI pipeline for building and deploying the registry, should NOT rely on the registry
Summary
In production#14260 (closed) a recent registry deployment caused all pulls of historic images to fail, reverting the deployment wasnt possible as the CI pipeline to do so uses the registry itself for images eg (https://ops.gitlab.net/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/blob/master/.gitlab-ci.yml#L108)
Related Incident(s)
Originating issue(s): production#14260 (closed)
Desired Outcome/Acceptance Criteria
The registry deployment, and ideally build pipelines should no longer use the deployed production registry (staging, or another environment is acceptable)
Associated Services
Corrective Action Issue Checklist
-
Link the incident(s) this corrective action arose out of -
Give context for what problem this corrective action is trying to prevent from re-occurring -
Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4') -
Assign a priority (this will default to 'Reliability::P4')