diff options
| author | Lyle Kozloff <lkozloff@gitlab.com> | 2019-07-09 06:23:17 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-07-09 06:23:17 +0000 |
| commit | 3306aa860b1cb2b7c6bb973b17402eee8266f975 (patch) | |
| tree | ddbf834856b50b264bb9499d2448f59064fc1670 | |
| parent | b0cbab9cec7e500858e74b0ea018b1751e094529 (diff) | |
| download | gitlab-ce-3306aa860b1cb2b7c6bb973b17402eee8266f975.tar.gz | |
Makes copying host keys a recommended step
| -rw-r--r-- | doc/administration/high_availability/gitlab.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/high_availability/gitlab.md b/doc/administration/high_availability/gitlab.md index 3045be616a6..9b1b7142e83 100644 --- a/doc/administration/high_availability/gitlab.md +++ b/doc/administration/high_availability/gitlab.md @@ -125,7 +125,7 @@ need some extra configuration. from running on upgrade. Only the primary GitLab application server should handle migrations. -1. **Optional** Configure host keys. Copy all contents(primary and public keys) inside `/etc/ssh/` on +1. **Recommended** Configure host keys. Copy the contents (primary and public keys) of `/etc/ssh/` on the primary application server to `/etc/ssh` on all secondary servers. This prevents false man-in-the-middle-attack alerts when accessing servers in your High Availability cluster behind a load balancer. |