You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using Redis + Sentinel (v7.2.4) with non-TLS port currently. We'd like to introduce tls-port and gradually migrate our applications to use it. For the duration of migration we'd need to support both non-TLS and TLS ports. We expect it to work like this:
When the client connects to non-TLS Sentinel port and tries to get Redis master information, master IP and non-TLS port are returned
When the client connects to TLS Sentinel port and tries to get Redis master information, master IP and TLS port are returned
It seems that currently Sentinel returns master IP and non-TLS port in both cases:
Is it possible to configure Sentinel to return Redis master TLS port when client connects to Sentinel on TLS port? I see that similar functionality was recently introduced for Redis cluster: #12233
Relevant excerpt from redis config:
port 6385
bind <IP>
tls-port 8385
tls-cert-file /etc/redis/tls/<service-name>.crt
tls-key-file /etc/redis/tls/<service-name>.key
tls-auth-clients no
Hi 馃憢
We're using Redis + Sentinel (v7.2.4) with non-TLS port currently. We'd like to introduce
tls-port
and gradually migrate our applications to use it. For the duration of migration we'd need to support both non-TLS and TLS ports. We expect it to work like this:It seems that currently Sentinel returns master IP and non-TLS port in both cases:
Is it possible to configure Sentinel to return Redis master TLS port when client connects to Sentinel on TLS port? I see that similar functionality was recently introduced for Redis cluster: #12233
Relevant excerpt from redis config:
Relevant excerpt from sentinel config:
Please let me know if additional details are needed.
The text was updated successfully, but these errors were encountered: