diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md index afe2d88e390426beefdd33937cbcfecf42c1a4b2..b453cbca74a7a1900e38fe241f30bc7e138c61b1 100644 --- a/doc/administration/reference_architectures/10k_users.md +++ b/doc/administration/reference_architectures/10k_users.md @@ -2446,3 +2446,12 @@ An example for the GitLab Helm Charts targetting the above 200 RPS or 10,000 ref Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/1k_users.md b/doc/administration/reference_architectures/1k_users.md index ecd82b341b481ec596473ef53d2f0e98af48b417..aad4cda1de79baf788b7d448823ef7f48ae2c793 100644 --- a/doc/administration/reference_architectures/1k_users.md +++ b/doc/administration/reference_architectures/1k_users.md @@ -129,3 +129,12 @@ and _stateful_ components are deployed in compute VMs with the Linux package. The [2k or 40 RPS GitLab Cloud Native Hybrid](2k_users.md#cloud-native-hybrid-reference-architecture-with-helm-charts-alternative) (non HA) and [3k or 60 RPS GitLab Cloud Native Hybrid](3k_users.md#cloud-native-hybrid-reference-architecture-with-helm-charts-alternative) (HA) reference architectures are the smallest we recommend in Kubernetes. For environments that serve fewer users or a lower RPS, you can lower the node specs. Depending on your user count, you can lower all suggested node specs as desired. However, it's recommended that you don't go lower than the [general requirements](../../install/requirements.md). + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md index 2eba5f563ab9c40cc0dc6690135b790d5050ec64..a083b5198dbf07ae84c62a07856fbe16078a5536 100644 --- a/doc/administration/reference_architectures/25k_users.md +++ b/doc/administration/reference_architectures/25k_users.md @@ -2453,3 +2453,12 @@ An example for the GitLab Helm Charts targetting the above 500 RPS or 25,000 ref Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md index 169220c9093c231f80db78e9f07b23e1b36db47d..e9be9dcae4430e9f67c3a9a3e720bcebe5ee0c94 100644 --- a/doc/administration/reference_architectures/2k_users.md +++ b/doc/administration/reference_architectures/2k_users.md @@ -1244,3 +1244,12 @@ An example for the GitLab Helm Charts for the above 40 RPS or 2,000 reference ar Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index 692b01012715f264dfb28d9d86baca073292fc72..827e687efb2352012ea5cfdfeb6e467f28acd86f 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -2116,16 +2116,19 @@ supported modifications you can make to this architecture to reduce complexity a It should be noted that to achieve HA with GitLab, the 60 RPS or 3,000 users architecture's makeup is ultimately what is required. Each component has various considerations and rules to follow, and the architecture meets all of these. Smaller versions of this architecture will be fundamentally the same, -but with smaller performance requirements, several modifications can be considered as follows: +but with smaller performance requirements, the following modifications are supported as follows: + +NOTE: +If not stated below, no other modifications are supported for lower use counts. - Lowering node specs: Depending on your user count, you can lower all suggested node specs as desired. However, it's recommended that you don't go lower than the [general requirements](../../install/requirements.md). -- Combining select nodes: Some nodes can be combined to reduce complexity at the cost of some performance: +- Combining select nodes: The following specific components are supported to be combined onto the same nodes to reduce complexity at the cost of some performance: - GitLab Rails and Sidekiq: Sidekiq nodes can be removed, and the component instead enabled on the GitLab Rails nodes. - PostgreSQL and PgBouncer: PgBouncer nodes could be removed and instead be enabled on PostgreSQL nodes with the Internal Load Balancer pointing to them. However, to enable [Database Load Balancing](../postgresql/database_load_balancing.md), a separate PgBouncer array is still required. - Reducing the node counts: Some node types do not need consensus and can run with fewer nodes (but more than one for redundancy). This will also lead to reduced performance. - GitLab Rails and Sidekiq: Stateless services don't have a minimum node count. Two are enough for redundancy. - PostgreSQL and PgBouncer: A quorum is not strictly necessary. Two PostgreSQL nodes and two PgBouncer nodes are enough for redundancy. -- Running select components in reputable Cloud PaaS solutions: Select components of the GitLab setup can instead be run on Cloud Provider PaaS solutions. By doing this, additional dependent components can also be removed: +- Running select components in reputable Cloud PaaS solutions: The following specific components are supported to be run on reputable Cloud Provider PaaS solutions. By doing this, additional dependent components can also be removed: - PostgreSQL: Can be run on reputable Cloud PaaS solutions such as Google Cloud SQL or Amazon RDS. In this setup, the PgBouncer and Consul nodes are no longer required: - Consul may still be desired if [Prometheus](../monitoring/prometheus/index.md) auto discovery is a requirement, otherwise you would need to [manually add scrape configurations](../monitoring/prometheus/index.md#adding-custom-scrape-configurations) for all nodes. - As Redis Sentinel runs on the same box as Consul in this architecture, it may need to be run on a separate box if Redis is still being run using the Linux package. @@ -2338,3 +2341,12 @@ An example for the GitLab Helm Charts for the above 60 RPS or 3,000 reference ar Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md index 406360ee54df3671396cadc74a8cbda3f0e20ba3..5499ec5e619199435bd5254b696283a4c8ac51a3 100644 --- a/doc/administration/reference_architectures/50k_users.md +++ b/doc/administration/reference_architectures/50k_users.md @@ -2467,3 +2467,12 @@ An example for the GitLab Helm Charts targetting the above 1000 RPS or 50,000 re Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md index 26cd85cfb322c425df7fa0cbc2ffca5ad9d66186..8a9a384da85bf319a8275206cb06512681e3d89e 100644 --- a/doc/administration/reference_architectures/5k_users.md +++ b/doc/administration/reference_architectures/5k_users.md @@ -2314,3 +2314,12 @@ An example for the GitLab Helm Charts targetting the above 100 RPS or 5,000 refe Back to set up components + +## Next steps + +After following this guide you should now have a fresh GitLab environment with core functionality configured accordingly. + +You may want to configure additional optional features of GitLab depending on your requirements. See [Steps after installing GitLab](../../install/next_steps.md) for more information. + +NOTE: +Depending on your environment and requirements, additional hardware requirements or adjustments may be required to set up additional features as desired. Refer to the individual pages for more information. diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index 8520f1924663ae4f9853c5a0dec3e7a2bb7ccc2f..718675c7593dc02e217975f53c5e048ba797fc69 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -776,6 +776,7 @@ You can find a full history of changes [on the GitLab project](https://gitlab.co **2024:** +- [2024-08](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/162144): Added Next Steps breadcrumb section to the pages to help discoverability of additional features. - [2024-05](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153716): Updated the 60 RPS / 3k User and 100 RPS / 5k User pages to have latest Redis guidance on co-locating Redis Sentinel with Redis itself. - [2024-05](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153579): Renamed `Cost to run` section to `Cost calculator templates` to better reflect the calculators are only a starting point and need to be adjusted with specific usage to give more accurate cost estimates. - [2024-04](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149878): Updated recommended sizings for Webservice nodes for Cloud Native Hybrids on GCP. Also adjusted NGINX pod recommendation to be run on Webservice node pool as a DaemonSet. diff --git a/doc/install/next_steps.md b/doc/install/next_steps.md index 76416408facc750c5bf35af50516c8472486d011..346841f5fbcbb5148a9cb15ec5cf2718f484a190 100644 --- a/doc/install/next_steps.md +++ b/doc/install/next_steps.md @@ -17,19 +17,24 @@ installation. - [SMTP](https://docs.gitlab.com/omnibus/settings/smtp.html): Configure SMTP for proper email notifications support. +- [Incoming email](../administration/incoming_email.md): Configure incoming email + so that users can use email to reply to comments, create new issues and merge requests, etc. -## CI/CD +## CI/CD (Runner) - [Set up runners](https://docs.gitlab.com/runner/): Set up one or more runners, the agents that are responsible for running CI/CD jobs. -- [GitLab Pages](../administration/pages/index.md): Configure GitLab Pages to - allow hosting of static sites. -- [GitLab Registry](../administration/packages/container_registry.md): Set up the - GitLab container registry so every project can have its own space to store Docker - images. + +## Container Registry + +- [Container Registry](../administration/packages/container_registry.md): Integrated container registry to store container images for each GitLab project. - [GitLab Dependency Proxy](../administration/packages/dependency_proxy.md): Set up the dependency proxy so you can cache container images from Docker Hub for faster, more reliable builds. +## Pages + +- [GitLab Pages](../user/project/pages/index.md): Publish static websites directly from a repository in GitLab + ## Security - [Secure GitLab](../security/index.md):