Verified Commit 17234a9f authored by Andreas Brandl's avatar Andreas Brandl
Browse files

Update links and images for GitLab Dedicated team move 

Update all internal links pointing to the old infrastructure/team/gitlab-dedicated
path to use the new infrastructure-platforms/gitlab-dedicated path.

Move images to match new structure:
- From: static/images/engineering/infrastructure/team/gitlab-dedicated/
- To: static/images/engineering/infrastructure-platforms/gitlab-dedicated/

Files with updated page links (7 files):
- support/workflows/saas_sm_cheatsheet.md
- security/identity/kingdoms/_index.md
- hiring/interviewing/infrastructure-interview.md
- security/identity/counterparts/_index.md (4 links)
- support/workflows/dedicated_instance_health.md
- legal/privacy/customer-product-usage-information.md
- engineering/releases/internal-releases/index.md

Files with updated image paths (2 files):
- gitlab-dedicated/architecture/_index.md
- gitlab-dedicated/architecture/from-dedicated-to-cells-technical-analysis.md

Images moved (20 files):
- architecture/*.png (8 files)
- *.png (12 files including logos, labels, cloud providers)

Also extended redirect expiry date to 2026-06-01 in layouts/index.redirects.
parent 508ee6f1

.gitlab/CODEOWNERS

+0 −1
Original line number Diff line number Diff line
@@ -197,7 +197,6 @@ 
/content/handbook/engineering/infrastructure/team/ @marin

/content/handbook/engineering/infrastructure-platforms/andrew-newdigate.md @andrewn

/content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/ @marin @fviegas

/content/handbook/engineering/infrastructure/team/gitlab-dedicated/ @marin @fviegas

/content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/environment-automation.md @o-lluch @denhams @marin @fviegas

/content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/switchboard.md @ashiel @marin @fviegas

/content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/us-public-sector-services.md @marin @fviegas @mckgl

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/architecture/_index.md

+1 −1
Original line number Diff line number Diff line
@@ -2,7 +2,7 @@ 
title: "GitLab Dedicated Architecture"

---



![GitLab Dedicated Group logo](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/dedicated_team_logo.png)

![GitLab Dedicated Group logo](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/dedicated_team_logo.png)



## Architecture

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/architecture/from-dedicated-to-cells-technical-analysis.md

+7 −7
Original line number Diff line number Diff line
@@ -37,7 +37,7 @@ For Terraform and Chef, each of these environments is unique, although they shar 
ensure consistency. However, each environment can differ from the others. There is no way to ensure uniformity, and over time

these environments have, for a variety of reasons, drifted away from uniformity.



![Config MGMT](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/envs-in-gitlab-com-config-mgmt.png)

![Config MGMT](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/envs-in-gitlab-com-config-mgmt.png)



*Similar but different: environments in GitLab.com's config-mgmt project*
@@ -49,8 +49,8 @@ are not replicas of one another, or the same configuration with different input 
smaller/cheaper copy of Production). They are two distinctive environments, built in parallel to one another.



<p float="middle">

  <img alt="GKE Zonal Configuration for Staging" src="/images/engineering/infrastructure/team/gitlab-dedicated/architecture/gke-zonal-conf-gstg.png" width="49%" />

  <img alt="GKE Zonal Configuration for Production" src="/images/engineering/infrastructure/team/gitlab-dedicated/architecture/gke-zonal-conf-gprd.png" width="49%" />

  <img alt="GKE Zonal Configuration for Staging" src="/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/gke-zonal-conf-gstg.png" width="49%" />

  <img alt="GKE Zonal Configuration for Production" src="/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/gke-zonal-conf-gprd.png" width="49%" />

</p>



*Same Same, but Different: the GKE Zonal Configuration for Staging and Production. Similar, but not the same.*
@@ -82,7 +82,7 @@ coordination needs to be carried out to ensure that change is done in the correc 
may need to be applied, followed by chef-repo changes. If differences happen to occur in the manual coordination of these changes,

it may lead to unexpected outcomes, ultimately leading to slower delivery, outages or even data-loss.



![Many congif mngmt tools](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/many-config-mngmt-tools.png)

![Many congif mngmt tools](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/many-config-mngmt-tools.png)



*GitLab.com: Many Different Configuration Management Tools*
@@ -91,7 +91,7 @@ it may lead to unexpected outcomes, ultimately leading to slower delivery, outag 
Dedicated seeks to simplify this model by providing a single project, Instrumentor, which encapsulates all atomic changes to

the tenant or cell environment. The problem of coordinating changes across multiple projects is solved by integrating all changes into a single project.



![Dedicated single poe for all envs](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/dedicated-single-poe-for-all-envs.png)

![Dedicated single poe for all envs](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/dedicated-single-poe-for-all-envs.png)



*Dedicated: Single Entrypoint for All Environment Changes*
@@ -156,7 +156,7 @@ and adding the features to support this would add a great deal of complexity tha 


This section describes the components of GitLab Dedicated, focusing on why these components were included in the design.



![GitLab Dedicated components](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/gitlab-dedicated-components.png)

![GitLab Dedicated components](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/gitlab-dedicated-components.png)



*GitLab Dedicated Components*
@@ -261,7 +261,7 @@ Many of the same design considerations that apply for GitLab Dedicated apply equ 


Cells could use the same deployment model as Environment Automation used before Switchboard had been developed. This is represented by the switchboard_la project.



![Cells deployments via env automation](/images/engineering/infrastructure/team/gitlab-dedicated/architecture/cells-deployments-via-environment-automation.png)

![Cells deployments via env automation](/images/engineering/infrastructure-platforms/gitlab-dedicated/architecture/cells-deployments-via-environment-automation.png)



*Deploying Cells using Environment Automation*

content/handbook/engineering/releases/internal-releases/index.md

+1 −1
Original line number Diff line number Diff line
@@ -41,7 +41,7 @@ An internal release has the following phases: 
   * Critical bug: The Dedicated team reports a high-severity issue causing a performance degradation.



2. **Prepare**: The first step in the internal release process, when a release issue is created and stakeholders,

   including the [GitLab Dedicated Group](/handbook/engineering/infrastructure/team/gitlab-dedicated) are notified.

   including the [GitLab Dedicated Group](/handbook/engineering/infrastructure-platforms/gitlab-dedicated) are notified.



3. **GitLab.com remediation**:

   * The group relevant to the vulnerability/bug prepares the security fix on the GitLab security repositories.

content/handbook/hiring/interviewing/infrastructure-interview.md

+1 −1
Original line number Diff line number Diff line
@@ -24,7 +24,7 @@ If you choose to, you can learn even more about the infrastructure department an 


- [SaaS Platforms](/handbook/engineering/infrastructure/team/platforms/)

  - [Delivery Group](/handbook/engineering/infrastructure-platforms/gitlab-delivery/delivery/)

  - [Dedicated Group](/handbook/engineering/infrastructure/team/gitlab-dedicated/)

  - [Dedicated Group](/handbook/engineering/infrastructure-platforms/gitlab-dedicated/)

  - [Production Engineering Group](/handbook/engineering/infrastructure-platforms/production-engineering/)



A well-written resume or a detailed LinkedIn profile will increase your chances to be selected for this role. Read the requirements carefully and make sure that some of those specific areas are outlined in your resume/LinkedIn profile. In Infrastructure Engineering, we especially pay attention to your experience/knowledge of: