chore: Cleanup redis usage and language for clarity (#1339)

* chore: Cleanup redis usage and language for clarity

* fix: use fqdn

Author: gavinelder

platform-enterprise_docs/enterprise/_templates/docker/docker-compose.yml

@@ -27,7 +27,14 @@ services:
       - $HOME/.tower/db/mysql:/var/lib/mysql
 
   redis:
-    image: cr.seqera.io/public/redis:7.0.10
+    # This Redis definition is provided for convenience and pulls from Docker
+    # Hub's public registry. For production use we recommend:
+    #   - Vendoring this image to your own registry, or authenticating to Docker
+    #     Hub to avoid pull rate limits.
+    #   - Replacing this in-cluster instance with a managed service (e.g.
+    #     ElastiCache, Azure Cache for Redis, Memorystore) or an official Redis
+    #     installation source for durability and operational support.
+    image: docker.io/library/redis:7.4
     platform: linux/amd64
     networks:
       - backend

platform-enterprise_docs/enterprise/_templates/k8s/redis.aks.yml

@@ -32,6 +32,10 @@ See [Database configuration](./configuration/overview#seqera-and-redis-databases
 
 ## Redis configuration
 
+:::info
+The bundled `redis` container in `docker-compose.yml` is intended for evaluation and small workloads. For production, use a managed service or an [official Redis installation source](https://redis.io/docs/latest/operate/oss_and_stack/install/).
+:::
+
 Configure the Redis connection URL in your Seqera environment:
 
 ```bash
@@ -52,7 +56,7 @@ Use a managed Redis service for production:
 
 3. Download and configure the [docker-compose.yml](_templates/docker/docker-compose.yml) file:
 
-      - The `db` container should be used only for local testing. If you have configured this service elsewhere, you can remove this container.
+      - The `db` and `redis` containers should be used only for local testing. If you have configured these services elsewhere, you can remove these containers.
 
       - To configure the Seqera pipeline optimization service (`groundswell`), see [Pipeline optimization](./configuration/pipeline_optimization).
 

platform-enterprise_docs/enterprise/_templates/k8s/redis.eks.yml

@@ -9,14 +9,15 @@ Kubernetes deployments are recommended for production workloads requiring high a
 
 :::info Prerequisites <span id="prerequisites" />
 Other than the basic requirements [already listed in the Platform installation overview](./install-platform#prerequisites), you will need:
+
 - A Kubernetes cluster
 - [kubectl](https://kubernetes.io/docs/tasks/tools/) installed locally
 :::
 
 ### Recommended resources
 
-| Component | CPU | Memory |
-| :-------- | :-- | :----- |
+| Component   | CPU    | Memory                    |
+| :---------- | :----- | :------------------------ |
 | Backend pod | 1 core | 4000 Mi request and limit |
 
 ## Container images
@@ -48,6 +49,7 @@ TOWER_REDIS_URL=redis://<redis-host>:6379
 ```
 
 Use a managed Redis service for production:
+
 - [Amazon ElastiCache](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatIs.html) (`cache.m4.large` or larger)
 - [Azure Cache for Redis](https://learn.microsoft.com/en-gb/azure/azure-cache-for-redis/cache-overview) (C3 tier or larger)
 - [Google Memorystore](https://cloud.google.com/memorystore/docs/redis) (M2 tier or larger)