docs: Redis Cluster announce endpoint guide for external access (#131)

Signed-off-by: Arnob Kumar Saha <arnob@appscode.com>

Author: ArnobKumarSaha

docs/platform/guides/database-management/create-database/redis.md

@@ -32,10 +32,33 @@ Select the topology under **Database Mode**. Three modes are available:
 | **Cluster** | **Master** count and **Replicas** per master. |
 | **Sentinel** | **Number of Replicas** and the referenced **Sentinel** instance. |
 
+## Announce Redis Endpoints (Cluster Mode Only)
+
+> **Important — required if you plan to expose a Cluster-mode Redis externally.** The default external endpoint (via **Expose via Gateway**, see [Additional Options](common-steps.md#6-additional-options)) is a single Kubernetes Service that load-balances across *all* pods in *all* shards. Redis Cluster clients don't work well with that: a client's request is only served correctly if the pod it happens to connect to owns the requested key's slot — otherwise Redis replies with a redirect to the internal pod IP, which the external client cannot reach and the connection times out.
+>
+> Toggling on **Announce Redis Endpoints** tells each Redis node to advertise its externally reachable address instead of its internal IP, so redirects point somewhere the client can actually connect to.
+
+If **Database Mode** is **Cluster**, an **Announce Redis Endpoints ?** toggle appears below **Storage Size**. Turn it on to reveal the **Announce** panel:
+
+![Announce Redis Endpoints toggle and Announce panel with Type and per-shard endpoints](../images/db-create/redis/announce.png)
+
+| Field | Description |
+|---|---|
+| **Type** | How the endpoint is advertised to clients — `hostname` or `ip`. Ask your cluster administrator which one your externally reachable Redis endpoints use. |
+| **Shards** | One row per shard, in the same order the shards are provisioned (shard 0, shard 1, …). Each row's **Shard Endpoints** field takes a comma-separated list of the externally reachable endpoints for every node (master + replicas) in that shard. Use **+ Add new** to add a row if you have more shards than rows shown. |
+
+The number of shard rows must match the **Shards** count you set above, and each row must list one endpoint per node in that shard (master + replicas).
+
+Whatever the **Type** (`hostname` or `ip`), the values you enter must ultimately resolve to the envoy service's external IP. For `hostname`, point a DNS **A** or **CNAME** record at that IP; for `ip`, enter the envoy service's IP directly. When exposure is enabled, envoy opens a set of ports on its external IP — one per Redis pod — and clients reach each pod through its assigned port.
+
+> **Note:** This only applies when you intend to connect to a **Cluster**-mode Redis from outside Kubernetes. If you only access it from within the cluster, or you're using **Standalone**/**Sentinel** mode, leave this off.
+
+For the underlying mechanism, see the [Redis External Connections guide](https://kubedb.com/docs/v2026.6.19/guides/redis/external-connections/exposure/).
+
 ## Create a Redis Database
 
 1. Open the wizard and select **Redis** — see [Getting Started](common-steps.md#1-getting-started) and [Select a Database Type](common-steps.md#2-select-a-database-type).
 1. Set the [namespace and name](common-steps.md#3-choose-namespace-and-name).
-1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](common-steps.md#4-configure-the-database).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](common-steps.md#4-configure-the-database). For **Cluster** mode, configure [Announce Redis Endpoints](#announce-redis-endpoints-cluster-mode-only) if you'll expose it externally.
 1. Optionally configure [Advanced Configuration](common-steps.md#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](common-steps.md#6-additional-options) (monitoring, backup, TLS, gateway).
 1. Click [**Deploy**](common-steps.md#7-deploy).