diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-28 09:09:56 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-28 09:09:56 +0300 |
| commit | 1d42c38d9b4d4ca651db435c8eb0c47bd24a25e2 (patch) | |
| tree | add5ce3542470c7d3626c5669898ca3546f29285 /doc/install/openshift_and_gitlab | |
| parent | 3f5f07675c4205c28791486d66bcbe80b7e0eca4 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/install/openshift_and_gitlab')
| -rw-r--r-- | doc/install/openshift_and_gitlab/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/openshift_and_gitlab/index.md b/doc/install/openshift_and_gitlab/index.md index 022e2095c68..ecce211b65e 100644 --- a/doc/install/openshift_and_gitlab/index.md +++ b/doc/install/openshift_and_gitlab/index.md @@ -372,7 +372,7 @@ running scaled to 2. Upping the GitLab pods is actually like adding new application servers to your cluster. You can see how that would work if you didn't use GitLab with -OpenShift by following the [HA documentation](../../administration/high_availability/gitlab.md) for the application servers. +OpenShift by following the [HA documentation](../../administration/reference_architectures/index.md) for the application servers. Bare in mind that you may need more resources (CPU, RAM, disk space) when you scale up. If a pod is in pending state for too long, you can navigate to |