Skip to content

Commit b222514

Browse files
committed
docs(redis): document TLS limitations and connection patterns
Spell out which endpoints serve TLS (master/replicas ClusterIP on 6380), why Sentinel-aware clients cannot use TLS today, and how applications should connect to keep automatic master failover under TLS. Signed-off-by: Arsolitt <[email protected]>
1 parent e9e74a1 commit b222514

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

‎packages/apps/redis/values.yaml‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,11 @@ authEnabled: true
5656
## @field {string} secretName - Name of an existing kubernetes.io/tls secret. When non-empty, cert-manager Certificate is NOT rendered and the user manages the secret.
5757
## @field {TLSIssuerRef} issuerRef - cert-manager Issuer reference. Used only when secretName is empty.
5858

59+
## TLS limitations:
60+
## - Internal connections must use <release>-master:6380 (writes) or <release>-replicas:6380 (reads). Direct connection only — no Sentinel-aware service discovery over TLS.
61+
## - Sentinel HA clients (rfs-*:26379) operate on plaintext and resolve master IP as <ip>:6379 (the operator hardcodes the plaintext port). To use Sentinel-aware clients with TLS, the operator would need patching — out of scope.
62+
## - For applications that need automatic master failover with TLS: use <release>-master:6380 (the K8s Service's selector follows the master role label, so it auto-routes to the new master after failover).
63+
5964
## @param {TLS} tls - TLS configuration for client-facing connections. When enabled, an nginx stream sidecar terminates TLS on port 6380. Intra-cluster traffic on 6379 (operator probes, sentinel, replication) remains plaintext.
6065
tls:
6166
enabled: false

0 commit comments

Comments
 (0)