feat: update Redis helm chart docs and network policies lab

docs/for-devs/console/catalog.md

@@ -32,9 +32,9 @@ The `knative-service` Helm chart can be used to create a Knative `Service` (to d
 
 The `postgresql-cluster` Helm chart can be used to create a cloudnativepg PostgreSQL `Cluster`. Optionally a Prometheus `PodMonitor` and a `Configmap` (for adding a postgresql dashboard to Grafana) can be created.
 
-6. Redis master-replica cluster
+6. Redis high availability cluster
 
-The `redis-cluster` Helm chart can be used to create a Redis master-replica cluster.
+The `redis-ha` Helm chart can be used to create a Redis high availability cluster with master-replica topology and HAProxy load balancer.
 
 7. RabbitMQ Cluster and/or Queues
 

docs/for-ops/how-to/use-catalog.md

@@ -40,7 +40,7 @@ The `postgresql-cluster` Helm chart can be used to create a cloudnativepg Postgr
 
 ### quickstart-redis
 
-The `redis-cluster` Helm chart can be used to create a Redis master-replica cluster.
+The `redis-ha` Helm chart can be used to create a Redis high availability cluster with master-replica topology and HAProxy load balancer.
 
 ## Customize the catalog
 

docs/get-started/labs/create-netpols.md

@@ -44,8 +44,8 @@ Outbound Rules let you:
 
 ### 2. Deploy Redis & Postgres
 
-1. In the Catalog, install **redis** (master‑replica) with `auth.enabled=false`.
-2. Install **postgresql** with default settings.
+1. In the Catalog, install **redis** (redis-ha) with default settings.
+2. Install **postgresql** (postgresql-cluster) with default settings.
 
 ### 3. Deploy your workloads
 
@@ -64,7 +64,7 @@ containerPorts:
     protocol: TCP
 env:
   - name: REDIS_HOST
-    value: <redis-cluster-name>-quickstart-redis-master
+    value: <redis-ha-name>
 replicaCount: 1
 ```
 
@@ -91,7 +91,7 @@ env:
         name: <psql-cluster-name>-app
         key: password
   - name: REDIS_HOST
-    value: <redis-cluster-name>-quickstart-redis-master
+    value: <redis-ha-name>
   - name: DATABASE_HOST
     value: <psql-cluster-name>-rw
 replicaCount: 1
@@ -172,8 +172,12 @@ You’ll allow only Worker & Result to reach Postgres, and only Vote & Worker to
 2. **Name:** `redis-ingress`
 3. **Sources:**
 
-   - Workload: **worker** → `otomi.io/app=worker`
-   - ADD SOURCE → **vote** → `otomi.io/app=vote`
+   - **Workload:** select **worker**
+   - **Label(s):** Select `otomi.io/app=worker`from the drop-down
+   - Click **ADD SOURCE**, then add:
+
+     - **Workload:** vote
+     - **Label(s):** `otomi.io/app=vote`
 
 4. **Target:** Redis → `otomi.io/app=redis`
 5. **Save Changes**

docs/get-started/labs/use-catalog.md

@@ -30,9 +30,9 @@ The `knative-service` Helm chart can be used to create a Knative `Service` (to d
 
 The `postgresql-cluster` Helm chart can be used to create a cloudnativepg PostgreSQL `Cluster`. Optionally a Prometheus `PodMonitor` and a `Configmap` (for adding a postgresql dashboard to Grafana) can be created.
 
-### redis-cluster
+### redis-ha
 
-The `redis-cluster` Helm chart can be used to create a Redis master-replica cluster.
+The `redis-ha` Helm chart can be used to create a Redis high availability cluster with master-replica topology and HAProxy load balancer.
 
 ### rabbitmq-cluster