Skip to content

Commit 21f0e94

Browse files
docs: clarify Redis announce endpoint resolution to envoy IP
Signed-off-by: Arnob Kumar Saha <arnob@appscode.com>
1 parent 9a92a9f commit 21f0e94

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • docs/platform/guides/database-management/create-database

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ If **Database Mode** is **Cluster**, an **Announce Redis Endpoints ?** toggle ap
4949

5050
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).
5151

52-
You will need the externally reachable hostname or IP for every Redis pod before filling this in — get these from whoever set up the external gateway/DNS/load balancer for this cluster. All the underlying setup (gateway, DNS records, port mappings) is handled on the platform side; you only need to enter the resulting endpoints here.
52+
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.
5353

5454
> **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.
5555

0 commit comments

Comments
 (0)