Merge branch 'doc-reference-component-doc' into 'master'

Reference the add new component docs in more places

See merge request gitlab-org/gitlab!52934

doc/development/architecture.md

@@ -91,6 +91,8 @@ The simplest way to ensure this, is to add support for your feature or service t
 [the official GitLab Helm chart](https://docs.gitlab.com/charts/) or reach out to
 [the Distribution team](https://about.gitlab.com/handbook/engineering/development/enablement/distribution/#how-to-work-with-distribution).
 
+Refer to the [process for adding new service components](adding_service_component.md) for more details.
+
 ### Simplified component overview
 
 This is a simplified architecture diagram that can be used to

doc/development/code_review.md

@@ -122,6 +122,7 @@ with [domain expertise](#domain-experts).
 1. If your merge request includes a new or updated [application limit](https://about.gitlab.com/handbook/product/product-processes/#introducing-application-limits), it must be **approved by a [product manager](https://about.gitlab.com/company/team/)**.
 1. If your merge request includes Product Intelligence (telemetry or analytics) changes, it should be reviewed and approved by a [Product Intelligence engineer](https://gitlab.com/gitlab-org/growth/product_intelligence/engineers).
 1. If your merge request includes an addition of, or changes to a [Feature spec](testing_guide/testing_levels.md#frontend-feature-tests), it must be **approved by a [Quality maintainer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_qa) or [Quality reviewer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_qa)**.
+1. If your merge request introduces a new service to GitLab (Puma, Sidekiq, Gitaly are examples), it must be **approved by a [product manager](https://about.gitlab.com/company/team/)**. See the [process for adding a service component to GitLab](adding_service_component.md) for details.
 
 - (*1*): Please note that specs other than JavaScript specs are considered backend code.
 - (*2*): We encourage you to seek guidance from a database maintainer if your merge