From 1c745bb8d18a0c69c3ec3a2a25b4d6d8f3eac6a3 Mon Sep 17 00:00:00 2001 From: Grant Young Date: Fri, 29 Sep 2023 09:34:39 +0100 Subject: [PATCH 1/3] Add more guidance for external Redis services --- .../replication_and_failover_external.md | 38 +++++++++++++++++-- .../reference_architectures/10k_users.md | 14 ++++--- .../reference_architectures/25k_users.md | 14 ++++--- .../reference_architectures/2k_users.md | 7 +++- .../reference_architectures/3k_users.md | 7 +++- .../reference_architectures/50k_users.md | 14 ++++--- .../reference_architectures/5k_users.md | 7 +++- .../reference_architectures/index.md | 6 +++ 8 files changed, 83 insertions(+), 24 deletions(-) diff --git a/doc/administration/redis/replication_and_failover_external.md b/doc/administration/redis/replication_and_failover_external.md index 54d13991f3f64e..30ad36cb029bf6 100644 --- a/doc/administration/redis/replication_and_failover_external.md +++ b/doc/administration/redis/replication_and_failover_external.md @@ -32,14 +32,37 @@ Note the Redis node's IP address or hostname, port, and password (if required). 1. Configure the GitLab application servers with the appropriate connection details for your external Redis service in your `/etc/gitlab/gitlab.rb` file: + When using a single Redis instance: + ```ruby redis['enable'] = false - gitlab_rails['redis_host'] = 'redis.example.com' - gitlab_rails['redis_port'] = 6379 + gitlab_rails['redis_host'] = '' + gitlab_rails['redis_port'] = '' # Required if Redis authentication is configured on the Redis node - gitlab_rails['redis_password'] = 'Redis Password' + gitlab_rails['redis_password'] = '' + + # Set to true if instance is using Redis SSL + gitlab_rails['redis_ssl'] = true + ``` + + When using separate Redis Cache and Persistent instances: + + ```ruby + redis['enable'] = false + + # Default Redis connection + gitlab_rails['redis_host'] = '' + gitlab_rails['redis_port'] = '' + gitlab_rails['redis_password'] = '' + + # Set to true if instance is using Redis SSL + gitlab_rails['redis_ssl'] = true + + # Redis Cache connection + # Replace `redis://` with `rediss://` if using SSL + gitlab_rails['redis_cache_instance'] = 'redis://:@:' ``` 1. Reconfigure for the changes to take effect: @@ -48,6 +71,15 @@ Note the Redis node's IP address or hostname, port, and password (if required). sudo gitlab-ctl reconfigure ``` +### Setting the Redis Cache instance as an LRU + +When configuring a Redis Cache instance it should be configured as a [Least Recently Used cache](https://redis.io/docs/manual/eviction/) (LRU) accordingly. + +Configuring this depends on the cloud provider or service but generally the following settings and values will configure a cache: + +- `maxmemory-policy` = `allkeys-lru` +- `maxmemory-samples` = `5` + ## Redis replication and failover with your own Redis servers This is the documentation for configuring a scalable Redis setup when diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md index 39fc63f07fa074..5db8dd9d273526 100644 --- a/doc/administration/reference_architectures/10k_users.md +++ b/doc/administration/reference_architectures/10k_users.md @@ -39,7 +39,7 @@ full list of reference architectures, see 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. @@ -829,11 +829,15 @@ to be used with GitLab. The following IPs will be used as an example: - `10.6.0.62`: Redis - Persistent Replica 1 - `10.6.0.63`: Redis - Persistent Replica 2 -### Provide your own Redis instance +### Provide your own Redis instances -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Configure the Redis Cache cluster @@ -2272,7 +2276,7 @@ services where applicable): 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) and [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md index 15378cb6bb2bd0..5ceae6cc735916 100644 --- a/doc/administration/reference_architectures/25k_users.md +++ b/doc/administration/reference_architectures/25k_users.md @@ -39,7 +39,7 @@ full list of reference architectures, see 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. @@ -846,11 +846,15 @@ to be used with GitLab. The following IPs will be used as an example: - `10.6.0.62`: Redis - Persistent Replica 1 - `10.6.0.63`: Redis - Persistent Replica 2 -### Provide your own Redis instance +### Provide your own Redis instances -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Configure the Redis Cache cluster @@ -2291,7 +2295,7 @@ services where applicable): 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md index 6125b0a1dab214..2144840338d678 100644 --- a/doc/administration/reference_architectures/2k_users.md +++ b/doc/administration/reference_architectures/2k_users.md @@ -332,9 +332,12 @@ to be used with GitLab. ### Provide your own Redis instance -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Standalone Redis using the Linux package diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index a176065ced5085..8669a8de900a34 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -448,9 +448,12 @@ to be used with GitLab. The following IPs will be used as an example: ### Provide your own Redis instance -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Standalone Redis using the Linux package diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md index e1cab312374603..a07ae1875a3902 100644 --- a/doc/administration/reference_architectures/50k_users.md +++ b/doc/administration/reference_architectures/50k_users.md @@ -39,7 +39,7 @@ full list of reference architectures, see 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. @@ -839,11 +839,15 @@ to be used with GitLab. The following IPs will be used as an example: - `10.6.0.62`: Redis - Persistent Replica 1 - `10.6.0.63`: Redis - Persistent Replica 2 -### Provide your own Redis instance +### Provide your own Redis instances -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Configure the Redis Cache cluster @@ -2290,7 +2294,7 @@ services where applicable): 1. Can be optionally run on reputable third-party external PaaS PostgreSQL solutions. See [Provide your own PostgreSQL instance](#provide-your-own-postgresql-instance) for more information. -2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instance](#provide-your-own-redis-instance) for more information. +2. Can be optionally run on reputable third-party external PaaS Redis solutions. See [Provide your own Redis instances](#provide-your-own-redis-instances) for more information. - Redis is primarily single threaded. It's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. 3. Can be optionally run on reputable third-party load balancing services (LB PaaS). See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. 4. Should be run on reputable Cloud Provider or Self Managed solutions. See [Configure the object storage](#configure-the-object-storage) for more information. diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md index f35f8a192c505e..55c87d87032ca7 100644 --- a/doc/administration/reference_architectures/5k_users.md +++ b/doc/administration/reference_architectures/5k_users.md @@ -442,9 +442,12 @@ to be used with GitLab. The following IPs are used as an example: ### Provide your own Redis instance -You can optionally use a third party external service for Redis as long as it meets the [requirements](../../install/requirements.md#redis). +You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: -A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. However, note that the Redis Cluster mode specifically isn't supported by GitLab. See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +- A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. +- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. + +See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. ### Standalone Redis using the Linux package diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index c325c706c94360..293ec93ab1b95c 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -341,6 +341,12 @@ If you choose to use a third party external service: 1. However, if [Database Load Balancing](../postgresql/database_load_balancing.md) via Read Replicas is desired for further improved performance it's recommended to follow the node count for the Reference Architecture. 1. If [GitLab Geo](../geo/index.md) is to be used the service will need to support Cross Region replication +### Recommendation notes for the Redis services + +[When selecting to use an external Redis service](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider), it should run a standard, performant, and supported version. + +Please note that Redis is primarily single threaded. As such, for the 10,000 user and above Reference Architectures, it's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. + #### Unsupported database services Several database cloud provider services are known not to support the above or have been found to have other issues and aren't recommended: -- GitLab From b69a20ce81387b1c285c61ca3f45cd4486e68fdd Mon Sep 17 00:00:00 2001 From: Kassandra Svoboda Date: Mon, 2 Oct 2023 08:53:35 +0000 Subject: [PATCH 2/3] Apply 1 suggestion(s) to 1 file(s) --- doc/administration/reference_architectures/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index 293ec93ab1b95c..d75f11e22dac73 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -345,7 +345,7 @@ If you choose to use a third party external service: [When selecting to use an external Redis service](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider), it should run a standard, performant, and supported version. -Please note that Redis is primarily single threaded. As such, for the 10,000 user and above Reference Architectures, it's strongly recommended separating out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. +Redis is primarily single threaded. For the 10,000 user and above Reference Architectures, separate out the instances as specified into Cache and Persistent data to achieve optimum performance at this scale. #### Unsupported database services -- GitLab From ebaca61b0e551fa17e4fa50a8415671af95b129d Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Mon, 2 Oct 2023 20:27:40 +0000 Subject: [PATCH 3/3] Apply 10 suggestion(s) to 7 file(s) --- .../redis/replication_and_failover_external.md | 6 +++--- doc/administration/reference_architectures/10k_users.md | 6 +++--- doc/administration/reference_architectures/25k_users.md | 6 +++--- doc/administration/reference_architectures/2k_users.md | 4 ++-- doc/administration/reference_architectures/3k_users.md | 4 ++-- doc/administration/reference_architectures/50k_users.md | 6 +++--- doc/administration/reference_architectures/5k_users.md | 4 ++-- 7 files changed, 18 insertions(+), 18 deletions(-) diff --git a/doc/administration/redis/replication_and_failover_external.md b/doc/administration/redis/replication_and_failover_external.md index 30ad36cb029bf6..cfe5a3157d989a 100644 --- a/doc/administration/redis/replication_and_failover_external.md +++ b/doc/administration/redis/replication_and_failover_external.md @@ -57,7 +57,7 @@ Note the Redis node's IP address or hostname, port, and password (if required). gitlab_rails['redis_port'] = '' gitlab_rails['redis_password'] = '' - # Set to true if instance is using Redis SSL + # Set to true if instance is using Redis SSL gitlab_rails['redis_ssl'] = true # Redis Cache connection @@ -73,9 +73,9 @@ Note the Redis node's IP address or hostname, port, and password (if required). ### Setting the Redis Cache instance as an LRU -When configuring a Redis Cache instance it should be configured as a [Least Recently Used cache](https://redis.io/docs/manual/eviction/) (LRU) accordingly. +When configuring a Redis Cache instance, it should be configured as a [Least Recently Used cache](https://redis.io/docs/manual/eviction/) (LRU) accordingly. -Configuring this depends on the cloud provider or service but generally the following settings and values will configure a cache: +Configuring this depends on the cloud provider or service, but generally the following settings and values configure a cache: - `maxmemory-policy` = `allkeys-lru` - `maxmemory-samples` = `5` diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md index 5db8dd9d273526..160284f09128d3 100644 --- a/doc/administration/reference_architectures/10k_users.md +++ b/doc/administration/reference_architectures/10k_users.md @@ -834,10 +834,10 @@ to be used with GitLab. The following IPs will be used as an example: You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. -- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU). -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Configure the Redis Cache cluster diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md index 5ceae6cc735916..24ff205d91b7eb 100644 --- a/doc/administration/reference_architectures/25k_users.md +++ b/doc/administration/reference_architectures/25k_users.md @@ -851,10 +851,10 @@ to be used with GitLab. The following IPs will be used as an example: You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. -- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU). -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Configure the Redis Cache cluster diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md index 2144840338d678..8c2f465fc1df70 100644 --- a/doc/administration/reference_architectures/2k_users.md +++ b/doc/administration/reference_architectures/2k_users.md @@ -335,9 +335,9 @@ to be used with GitLab. You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Standalone Redis using the Linux package diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index 8669a8de900a34..daf7479f32f65f 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -451,9 +451,9 @@ to be used with GitLab. The following IPs will be used as an example: You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Standalone Redis using the Linux package diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md index a07ae1875a3902..db0e3fdef75104 100644 --- a/doc/administration/reference_architectures/50k_users.md +++ b/doc/administration/reference_architectures/50k_users.md @@ -844,10 +844,10 @@ to be used with GitLab. The following IPs will be used as an example: You can optionally use a [third party external service for the Redis Cache and Persistence instances](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. -- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU) +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. +- The Redis Cache instance should be configured accordingly to be an [Least Recently Used cache](../redis/replication_and_failover_external.md#setting-the-redis-cache-instance-as-an-lru) (LRU). -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Configure the Redis Cache cluster diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md index 55c87d87032ca7..ba71a3e28fd012 100644 --- a/doc/administration/reference_architectures/5k_users.md +++ b/doc/administration/reference_architectures/5k_users.md @@ -445,9 +445,9 @@ to be used with GitLab. The following IPs are used as an example: You can optionally use a [third party external service for the Redis instance](../redis/replication_and_failover_external.md#redis-as-a-managed-service-in-a-cloud-provider) with the following guidance: - A reputable provider or solution should be used for this. [Google Memorystore](https://cloud.google.com/memorystore/docs/redis/redis-overview) and [AWS ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) are known to work. -- Redis Cluster mode is specifically not supported but Redis Standalone with HA is. +- Redis Cluster mode is specifically not supported, but Redis Standalone with HA is. -See [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services) for more information. +For more information, see [Recommended cloud providers and services](index.md#recommended-cloud-providers-and-services). ### Standalone Redis using the Linux package -- GitLab