Commit 9d8a33dc authored by Cynthia "Arty" Ng's avatar Cynthia "Arty" Ng
Browse files

Move images to static folder and update lint checker

parent 8e812478
Loading
Loading
Loading
Loading
+1 −1
Changes for content/handbook/engineering/architecture/design-documents/capacity_planning/_index.md: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -45,7 +45,7 @@ For illustration, we can see a saturation forecast plot below for the `disk_spac
Within the 90 days forecast horizon, we predict a violation of the `soft` SLO (set at 85% saturation) and this resulted in the creation of a [capacity planning issue](https://gitlab.com/gitlab-com/gl-infra/capacity-planning/-/issues/1219) for further review and potential actions.
At present, the Scalability::Observability group reviews those issues and engages with the respective DRI for the service in question to remedy a saturation concern.

<img src="images/image-20230911144743188.png" alt="image-20230911144743188" style="zoom:67%;" />
<img src="/images/engineering/architecture/design-documents/capacity_planning/image-20230911144743188.png" alt="image-20230911144743188" style="zoom:67%;" />

For GitLab.com capacity planning, we operate Tamland from a scheduled CI pipeline with access to the central Thanos, which provides saturation and utilization metrics for GitLab.com.
The CI pipeline produces the desired report, exposes it on GitLab Pages and also creates capacity planning issues.
+1 −1
Changes for content/handbook/engineering/architecture/design-documents/observability_tracing/_index.md: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -66,7 +66,7 @@ Much of the proposed architecture already exists and is in operation for GitLab.

 The following diagram outlines the architecture for GitLab Observability Backend and how clients, including the GitLab UI, will interact with it.

<img src="./arch.png" alt="">
<img src="/images/engineering/architecture/design-documents/observability_tracing/arch.png" alt="">

### Key Components

+2 −2
Changes for content/handbook/engineering/infrastructure/team/gitlab-dedicated/architecture/from-dedicated-to-cells-technical-analysis.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -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="./img/gke-zonal-conf-gstg.png" width="49%" />
  <img alt="GKE Zonal Configuration for Production" src="./img/gke-zonal-conf-gprd.png" width="49%" />
  <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%" />
</p>

*Same Same, but Different: the GKE Zonal Configuration for Staging and Production. Similar, but not the same.*
+1 −1
Changes for content/handbook/engineering/workflow/related-workflows/index.md: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -7,7 +7,7 @@ At GitLab we have a number of engineering processes that we use on a daily basis

The diagram below shows how these processes interact with one another. Links to each process are available below the image.

<img src="engineering-processes.png" alt="">
<img src="/images/engineering/workflow/related-workflows/engineering-processes.png" alt="">

## Links

+1 −1
Changes for content/handbook/enterprise-data/organization/data-science/_index.md: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -108,7 +108,7 @@ Please refer to the [Data Science Initiatives Internal Handbook](https://interna

The Data Science Team follows [Cross-Industry standard process for data mining (CRISP-DM)](https://en.wikipedia.org/wiki/Cross-industry_standard_process_for_data_mining), which consists of 6 iterative phases:

<img align="right" src="CRISP-DM_Process_Diagram.png" alt="" width="500">
<img align="right" src="/images/enterprise-data/organization/data-science/CRISP-DM_Process_Diagram.png" alt="" width="500">

1. **Business Understanding**

Loading