Dedicated Tooling Resilient to GitLab.com outages

Overview

Dedicated tooling like https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/instrumentor/ are all hosted on GitLab.com. Since we are going to start operating GitLab.com with that tooling as well we need to remove the dependency on GitLab.com since we need to be able to operator GitLab.com without depending on GitLab.com.

We have a known working pattern at the moment where we mirror the repositories on https://ops.gitlab.net/ and use Docker images either from ops.gitlab.net or from GCP Artifact Registry.

Action Items

• Take inventory of all the Dedicated Projects that we are going to use
• Create Dedicated group structure in
• Set up mirroring for each project, ideally managed via https://gitlab.com/gitlab-com/gl-infra/infra-mgmt
  • Import Dedicated projects into infra-mgmt
  • Create Dedicated projects in Ops
  • Configure mirroring from Dedicated projects to the ops instance Dedicated projects
  • Ensure pipelines for Dedicated projects will not break current processes by running on the ops instance
• Update jobs that run instrumentor not to use docker images to GitLab.com registry. moved to separate issue: #25570 (closed)