Redis: workhorse configuration errors when Redis Sentinel configured, unless port provided
Summary
Using stable/redis 10.x.x
, we now have the ability to make use of in-cluster Sentinel. Doing this should be as simple as pointing to RELEASE-redis:26379
Service.
Currently, workhorse's configuration is rendered without a port, unless it is specified in the properties.
Sentinel = [ "tcp://master-redis:<nil>"
Steps to reproduce
Configure Redis for cluster/Sentinel, and set properties for global.redis.sentinels
Configuration used
global:
redis:
host: master-redis-headless
sentinels:
- host: master-redis
# note: no `port` set!
redis:
cluster:
enabled: true
slaveCount: 2
sentinel:
enabled: true
usePassword: false # currently needed, apparently.
Current behavior
Sentinel = [ "tcp://master-redis:<nil>"
Expected behavior
Sentinel = [ "tcp://master-redis:26379"
Versions
- Chart: 08a89e4a
- Platform: N/A
Relevant logs
time="2020-01-24T21:42:16Z" level=info msg=Starting build_time=20200121.214054 version=v8.19.0
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8aef30]