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
But when I am connecting above Redis Sentinel to Harbor Helm with Chart Version: 1.6.1 and App Version: 2.5.0 I am getting following error.
values.yaml in harbor helm chart:
redis:
external:
# support redis, redis+sentinel
# addr for redis: <host_redis>:<port_redis>
# addr for redis+sentinel: <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
addr: redis-sentinel-node-0.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-1.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-2.redis-sentinel-headless.harbor-space.svc.cluster.local:26379
Error:
k8s-user@minikube-ubuntu:~/harbor-setup/git/harbor-setup/Harbor$ k logs kla-harbor-core-7f595f567f-65tq6
2022-05-23T05:28:28Z [INFO] [/core/controllers/base.go:155]: Config path: /etc/core/app.conf
2022-05-23T05:28:29Z [INFO] [/core/main.go:180]: initializing cache ...
2022-05-23T05:28:29Z [ERROR] [/lib/cache/cache.go:110]: failed to ping redis+sentinel://redis-sentinel-node-0.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-1.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-2.redis-sentinel-headless.harbor-space.svc.cluster.local:26379/mymaster/0?idle_timeout_seconds=30, retry after 500ms : redigo: no sentinels available; last error: NOAUTH Authentication required.
2022-05-23T05:28:29Z [ERROR] [/lib/cache/cache.go:110]: failed to ping redis+sentinel://redis-sentinel-node-0.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-1.redis-sentinel-headless.harbor-space.svc.cluster.local:26379,redis-sentinel-node-2.redis-sentinel-headless.harbor-space.svc.cluster.local:26379/mymaster/0?idle_timeout_seconds=30, retry after 718.832613ms : redigo: no sentinels available; last error: NOAUTH Authentication required.
NOTE: If Bitnami Redis Sentinel Auth is disabled , --set sentinel.enabled=true --set auth.enabled=false --set auth.sentinel=false then Harbor is able to connect to Redis Sentinel properly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello All,
Greetings of the day !
Does Harbor 2.5.0 support
Bitnami Redis Sentinel Auth
enabled?Kindly help me to enable Sentinel Auth! Thanks in advance !
usecase:
I am using
Bitnami Redis Sentinel
helm with Chart Version :16.8.9
and App Version:6.2.7
.With the following configuration in values.yaml, the redis failover (i.e. switch-master) is working fine.
--set sentinel.enabled=true --set auth.enabled=true --set auth.sentinel=true
But when I am connecting above Redis Sentinel to Harbor Helm with Chart Version:
1.6.1
and App Version:2.5.0
I am getting following error.values.yaml in harbor helm chart:
Error:
Beta Was this translation helpful? Give feedback.
All reactions