In my situation, I am using Redis with Sentinel option enabled in Kubernetes. All sentinels (and Redis) are available at an internal service of "redis" and it is only necessary to define the single instance. However, when using Redis Sentinel, where the sentinel requires a password, the password may be passed via the configuration like this:
This information is then visible on the overview and diagnostics screen. This PR redacts the information before display. I did not create an associated "Issue" however.
In my situation, I am using Redis with Sentinel option enabled in Kubernetes. All sentinels (and Redis) are available at an internal service of "redis" and it is only necessary to define the single instance. However, when using Redis Sentinel, where the sentinel requires a password, the password may be passed via the configuration like this:
This information is then visible on the overview and diagnostics screen. This PR redacts the information before display. I did not create an associated "Issue" however.