Update documentation for NFS support removal
All threads resolved!
All threads resolved!
Compare changes
Files
6@@ -35,7 +35,6 @@ full list of reference architectures, see
@@ -227,9 +226,6 @@ To set up GitLab and its components to accommodate up to 10,000 users:
@@ -1759,9 +1755,8 @@ To configure Praefect with TLS:
@@ -1929,9 +1924,8 @@ run [multiple Sidekiq processes](../sidekiq/extra_sidekiq_processes.md).
@@ -2070,7 +2064,6 @@ On each node perform the following:
@@ -2081,9 +2074,7 @@ On each node perform the following:
@@ -2209,9 +2200,6 @@ To configure the Monitoring node:
@@ -2235,7 +2223,7 @@ NOTE:
@@ -2254,22 +2242,6 @@ GitLab Runner returns job logs in chunks which Omnibus GitLab caches temporarily
While sharing the job logs through NFS is supported, it's recommended to avoid the need to use NFS by enabling [incremental logging](../job_logs.md#incremental-logging-architecture) (required when no NFS node has been deployed). Incremental logging uses Redis instead of disk space for temporary caching of job logs.