3bce8e1dca
Change 4954e284b9 updated the redis
sentinel driver to apply auth/ssl settings for redis sentinel, based
on ones of redis, but this change broke the existing usage in kolla
deployments, which require redis with authentication enabled and
sentinel with authentication DISABLED.
This restores the old behavior, which do not enable authentication and
ssl for sentinel even when these for redis is enabled.
Closes-Bug: #2056656
Change-Id: I3047c80359df3dad64be041db6f4a3a6180479d6
23 lines
778 B
YAML
23 lines
778 B
YAML
---
|
|
features:
|
|
- |
|
|
The redis driver now supports the following options.
|
|
|
|
- ``sentinel_username``
|
|
- ``sentinel_parameters``
|
|
- ``sentinel_ssl``
|
|
|
|
fixes:
|
|
- |
|
|
The redis driver no longer enables authentication for redis sentinel when
|
|
authentication is enabled in redis. This was the previous behavior before
|
|
6.0.0, and was already required by some deployment tools like kolla. Now
|
|
authentication for redis sentinel is controlled by a separate options
|
|
(``sentinel_username`` and ``sentinel_password``).
|
|
|
|
- |
|
|
The redis driver no longer enables SSL for redis sentinel when SSL is
|
|
enabled in redis, to restore the compatibility with older versions. Now
|
|
SSL for redis sentinel is controlled by the separate ``sentinel_ssl``
|
|
option.
|