Commit 21b1fc4d authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Fix markdownlint and broken links

parent c863b073
--- ---
redirect_to: ../monitoring/prometheus/index.md#standalone-prometheus-using-onmibus-gitlab redirect_to: ../monitoring/prometheus/index.md
--- ---
This document was moved to [another location](../monitoring/prometheus/index.md#standalone-prometheus-using-onmibus-gitlab). This document was moved to [another location](../monitoring/prometheus/index.md).
...@@ -8,18 +8,18 @@ NFS can be used as an alternative for object storage but this isn't typically ...@@ -8,18 +8,18 @@ NFS can be used as an alternative for object storage but this isn't typically
recommended for performance reasons. Note however it is required for [GitLab recommended for performance reasons. Note however it is required for [GitLab
Pages](https://gitlab.com/gitlab-org/gitlab-pages/-/issues/196). Pages](https://gitlab.com/gitlab-org/gitlab-pages/-/issues/196).
For data objects such as LFS, Uploads, Artifacts, etc., an [Object Storage service](../object_storage.md) For data objects such as LFS, Uploads, Artifacts, etc., an [Object Storage service](object_storage.md)
is recommended over NFS where possible, due to better performance. is recommended over NFS where possible, due to better performance.
CAUTION: **Caution:** CAUTION: **Caution:**
From GitLab 13.0, using NFS for Git repositories is deprecated. In GitLab 14.0, From GitLab 13.0, using NFS for Git repositories is deprecated. In GitLab 14.0,
support for NFS for Git repositories is scheduled to be removed. Upgrade to support for NFS for Git repositories is scheduled to be removed. Upgrade to
[Gitaly Cluster](../gitaly/praefect.md) as soon as possible. [Gitaly Cluster](gitaly/praefect.md) as soon as possible.
NOTE: **Note:** NOTE: **Note:**
Filesystem performance has a big impact on overall GitLab Filesystem performance has a big impact on overall GitLab
performance, especially for actions that read or write to Git repositories. See performance, especially for actions that read or write to Git repositories. See
[Filesystem Performance Benchmarking](../operations/filesystem_benchmarking.md) [Filesystem Performance Benchmarking](operations/filesystem_benchmarking.md)
for steps to test filesystem performance. for steps to test filesystem performance.
## Known kernel version incompatibilities ## Known kernel version incompatibilities
...@@ -41,10 +41,10 @@ errors. ...@@ -41,10 +41,10 @@ errors.
## Fast lookup of authorized SSH keys ## Fast lookup of authorized SSH keys
The [fast SSH key lookup](../operations/fast_ssh_key_lookup.md) feature can improve The [fast SSH key lookup](operations/fast_ssh_key_lookup.md) feature can improve
performance of GitLab instances even if they're using block storage. performance of GitLab instances even if they're using block storage.
[Fast SSH key lookup](../operations/fast_ssh_key_lookup.md) is a replacement for [Fast SSH key lookup](operations/fast_ssh_key_lookup.md) is a replacement for
`authorized_keys` (in `/var/opt/gitlab/.ssh`) using the GitLab database. `authorized_keys` (in `/var/opt/gitlab/.ssh`) using the GitLab database.
NFS increases latency, so fast lookup is recommended if `/var/opt/gitlab` NFS increases latency, so fast lookup is recommended if `/var/opt/gitlab`
...@@ -147,7 +147,7 @@ From GitLab 12.7, Rugged auto-detection is disabled if Puma thread count is grea ...@@ -147,7 +147,7 @@ From GitLab 12.7, Rugged auto-detection is disabled if Puma thread count is grea
If you want to use Rugged with Puma, it is recommended to [set Puma thread count to 1](https://docs.gitlab.com/omnibus/settings/puma.html#puma-settings). If you want to use Rugged with Puma, it is recommended to [set Puma thread count to 1](https://docs.gitlab.com/omnibus/settings/puma.html#puma-settings).
If you want to use Rugged with Puma thread count more than 1, Rugged can be enabled using the [feature flag](../../development/gitaly.md#legacy-rugged-code) If you want to use Rugged with Puma thread count more than 1, Rugged can be enabled using the [feature flag](../development/gitaly.md#legacy-rugged-code)
If the Rugged feature flag is explicitly set to either true or false, GitLab will use the value explicitly set. If the Rugged feature flag is explicitly set to either true or false, GitLab will use the value explicitly set.
...@@ -269,7 +269,7 @@ NFS mount point is `/gitlab-nfs`. Then, add the following bind mounts in ...@@ -269,7 +269,7 @@ NFS mount point is `/gitlab-nfs`. Then, add the following bind mounts in
Using bind mounts will require manually making sure the data directories Using bind mounts will require manually making sure the data directories
are empty before attempting a restore. Read more about the are empty before attempting a restore. Read more about the
[restore prerequisites](../../raketasks/backup_restore.md). [restore prerequisites](../raketasks/backup_restore.md).
You can view information and options set for each of the mounted NFS file You can view information and options set for each of the mounted NFS file
systems by running `nfsstat -m` and `cat /etc/fstab`. systems by running `nfsstat -m` and `cat /etc/fstab`.
...@@ -294,7 +294,7 @@ provide configuration for [UDP log shipping](https://docs.gitlab.com/omnibus/set ...@@ -294,7 +294,7 @@ provide configuration for [UDP log shipping](https://docs.gitlab.com/omnibus/set
Having multiple NFS mounts will require manually making sure the data directories Having multiple NFS mounts will require manually making sure the data directories
are empty before attempting a restore. Read more about the are empty before attempting a restore. Read more about the
[restore prerequisites](../../raketasks/backup_restore.md). [restore prerequisites](../raketasks/backup_restore.md).
## NFS in a Firewalled Environment ## NFS in a Firewalled Environment
...@@ -353,7 +353,7 @@ Additionally, this configuration is specifically warned against in the ...@@ -353,7 +353,7 @@ Additionally, this configuration is specifically warned against in the
>to the NFS server can cause data corruption problems. >to the NFS server can cause data corruption problems.
For supported database architecture, please see our documentation on For supported database architecture, please see our documentation on
[Configuring a Database for GitLab HA](../postgresql/replication_and_failover.md). [Configuring a Database for GitLab HA](postgresql/replication_and_failover.md).
<!-- ## Troubleshooting <!-- ## Troubleshooting
...@@ -366,4 +366,3 @@ questions that you know someone might ask. ...@@ -366,4 +366,3 @@ questions that you know someone might ask.
Each scenario can be a third-level heading, e.g. `### Getting error message X`. Each scenario can be a third-level heading, e.g. `### Getting error message X`.
If you have none to add when creating a doc, leave this section in place If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. --> but commented out to help encourage others to add to it in the future. -->
...@@ -177,7 +177,7 @@ column. ...@@ -177,7 +177,7 @@ column.
| NFS ([5](#footnotes)) ([7](#footnotes)) | Shared disk storage service. Can be used as an alternative Object Storage. Required for GitLab Pages | [NFS configuration](../high_availability/nfs.md) | No | | NFS ([5](#footnotes)) ([7](#footnotes)) | Shared disk storage service. Can be used as an alternative Object Storage. Required for GitLab Pages | [NFS configuration](../high_availability/nfs.md) | No |
| [Consul](../../development/architecture.md#consul) ([3](#footnotes)) | Service discovery and health checks/failover | [Consul configuration](../high_availability/consul.md) **(PREMIUM ONLY)** | Yes | | [Consul](../../development/architecture.md#consul) ([3](#footnotes)) | Service discovery and health checks/failover | [Consul configuration](../high_availability/consul.md) **(PREMIUM ONLY)** | Yes |
| [PostgreSQL](../../development/architecture.md#postgresql) | Database | [PostgreSQL configuration](https://docs.gitlab.com/omnibus/settings/database.html) | Yes | | [PostgreSQL](../../development/architecture.md#postgresql) | Database | [PostgreSQL configuration](https://docs.gitlab.com/omnibus/settings/database.html) | Yes |
| [PgBouncer](../../development/architecture.md#pgbouncer) | Database connection pooler | [PgBouncer configuration](../high_availability/pgbouncer.md#running-pgbouncer-as-part-of-a-non-ha-gitlab-installation) **(PREMIUM ONLY)** | Yes | | [PgBouncer](../../development/architecture.md#pgbouncer) | Database connection pooler | [PgBouncer configuration](../postgresql/pgbouncer.md) **(PREMIUM ONLY)** | Yes |
| Repmgr | PostgreSQL cluster management and failover | [PostgreSQL and Repmgr configuration](../postgresql/replication_and_failover.md) | Yes | | Repmgr | PostgreSQL cluster management and failover | [PostgreSQL and Repmgr configuration](../postgresql/replication_and_failover.md) | Yes |
| Patroni | An alternative PostgreSQL cluster management and failover | [PostgreSQL and Patroni configuration](../postgresql/replication_and_failover.md#patroni) | Yes | | Patroni | An alternative PostgreSQL cluster management and failover | [PostgreSQL and Patroni configuration](../postgresql/replication_and_failover.md#patroni) | Yes |
| [Redis](../../development/architecture.md#redis) ([3](#footnotes)) | Key/value store for fast data lookup and caching | [Redis configuration](../high_availability/redis.md) | Yes | | [Redis](../../development/architecture.md#redis) ([3](#footnotes)) | Key/value store for fast data lookup and caching | [Redis configuration](../high_availability/redis.md) | Yes |
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment